What check proves
Verify proves the project’s configured automated checks pass. Check proves the behavior described by the active spec can actually be observed. Passing CI does not replace this behavioral evidence. For a rollback, check includes proving the removed behavior is gone and an unaffected regression path still works.
Evidence
Depending on the project, evidence can include:
- Browser navigation, clicks, forms, and screenshots
- Console and network error inspection
- CLI output and exit status
- API requests and response bodies
- Generated files or downloaded artifacts
Report
Check reports pass or fail for every done-when criterion. A failed criterion includes the observed result and the next fix target. Check does not edit source code or commit fixes.
Relationship to try
/check is the agent-side proof pass. /try creates a human walkthrough with exact commands, routes, clicks, expected results, and signs that something is wrong.