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.
Manual guide
Run /check guide in Claude Code or $check guide in Codex when you want instructions for trying the change yourself.
/check guide
/check guide latest
/check guide /settingsWith no scope, the guide uses active work or the most recent archive when no work is active. latest selects the latest archive even while a feature is active. A step, route, path, or command can narrow the guide.
The guide explains what to start, where to go, what to do, what to expect, and what would indicate a problem. It does not run the app or checks, edit files, write activity or spec status, or record acceptance. Only the selected mode’s instructions are loaded.
Default /check remains the agent’s verification pass. A generated guide is never proof that the user tested anything. The existing tryGuide configuration keys retain their policies and now select /check guide; the separate check gates still select verification.
The former /try command is replaced by /check guide. See migration guidance.