Guide
Check And Verify
Use `check` for fast validation and `verify` for higher-confidence release checks.
These two workflows are validation tiers.
Use check during normal development and promote to verify when the cost of failure is meaningfully higher.
When To Use Each
check: normal code changes, small bug fixes, narrow refactors.verify: deployment-affecting changes, migrations, auth or billing work, and cross-cutting refactors.- Promote from
checktoverifywhen validation signal is weak or release risk is non-trivial.
Expected Output
- Commands run
- Result summary
- Anything skipped
- Release blockers or warnings for
verify - Residual risk if validation is partial