Generates a Makefile with a check target that runs lint, vet, format
checks, vulnerability scanning, and tests specific to the project's
language(s). The result is committed to the repo and used by CI, pre-commit
hooks, and the advanced-review preflight gate.
Trigger
Activate when the user says: "project checks", "scaffold checks",
"add make check", or /project-checks.
Execution Flow
Step 1 - Detect languages
Scan the project root for marker files:
| Marker | Language |
|---|---|
go.mod |
Go |
pyproject.toml or setup.py |
Python |
package.json |
JavaScript/TypeScript |
Gemfile |
Ruby |
Cargo.toml |
Rust |
Multiple languages can be detected (e.g., Go backend + Python scripts).
Step 2 - Generate Makefile
Load the template for each detected language from templates/<lang>.mk.
Combine into a single Makefile with:
checktarget that depends on all language-specific sub-targets- Sub-targets:
lint,vet,fmt-check,vuln,test - Each sub-target runs the appropriate tool for the language
Step 3 - Handle existing Makefile
If a Makefile already exists:
- Show the diff (what targets would be added)
- Ask the user before modifying
- Merge new targets without touching existing ones
If no Makefile exists: generate it directly.
Step 4 - Report
Show what was generated and suggest next steps:
make checkto run all checks- Add to CI pipeline
- The advanced-review preflight will auto-detect and use it
Language Templates
Each template defines the standard tooling for that language. Templates are
in templates/<lang>.mk and use Make variables for tool paths so users can
override them.
When to Use
- New project that needs a standardized check target
- Existing project without a unified lint/test/vuln command
- After the advanced-review preflight says "no make check target found"
When NOT to Use
- Project already has a working
make checkor equivalent - CI-only checks that don't make sense locally