Build And Test Commands
The instruction file must include build and test commands that the agent can run. Without these, the agent can't verify its own changes work correctly.
Antipatterns
- Providing build commands in prose ("you can build by running the makefile") without a heading containing "Commands", "Build", "Testing", or "Setup". The check matches headings, not body text.
- Using a heading like "## Development" or "## Usage" that does not contain any of the matched terms. The heading must include one of the specific keywords.
- Documenting commands only in a README or separate file. The check targets the main instruction file.
Pass / Fail
Pass
# MyProject
## Commands
- `npm install` -- install dependencies
- `npm test` -- run test suite
Fail
# MyProject
## Conventions
Use ESLint for linting.
Prefer functional components.
Limitations
Checks for a heading containing "Commands", "Build", "Testing", or "Setup". Does not verify the section contains runnable commands.
