Repository Validation

This is the general-purpose fallback for deciding how to validate a change when nothing else has specified it. Repository instructions and documented validation commands take precedence over these defaults.

Proportionate means matching the checks' scope and cost to the blast radius of the change. Run the smallest sufficient set that covers the changed artifact and behavior, widening to integration or end-to-end checks as the change's reach grows.

Discover the Checks

1. Read applicable AGENTS.md, README, contributor guidance, and nearby automation before choosing commands.
2. Inspect changed file types and available configuration such as .editorconfig, package manifests, CI workflows, task runners, and formatter or linter settings.
3. Prefer an existing documented check over inventing a new one.

Choose Proportionate Validation