← ClaudeAtlas

verifylisted

Run /verify <feature> to prove a built feature meets its spec's acceptance criteria, or /verify review for a fresh-model code review before a PR. Never edits code.
rishabhsisodiya/stop-guessing · ★ 0 · AI & Automation · score 70
Install: claude install-skill rishabhsisodiya/stop-guessing
## What this skill does Confirms a change before it merges, in two modes. - **`/verify <feature>`** runs the real application and checks each acceptance criterion by observing behavior. Not by reading the code and concluding it looks right. - **`/verify review [feature]`** reads the diff as a senior engineer, on a **fresh model that did not write the code**, and reports what it finds. Default is run mode. `review` as the first word selects review mode. At `fast` tier neither is expected; `/develop`'s own self check is the check. At `strict`, run mode follows every build and review mode runs before a pull request. ## The rule that makes this worth running **A criterion is met only when it was observed being met.** Reading the code and concluding it should work is not verification, it is a second opinion from the same source that wrote it. If it could not be observed, it is `unverified`, and that word appears in the report. A verify pass that reports "all criteria met" without having driven the app is worse than no verify pass, because it converts an unknown into a false certainty. ## What this skill refuses to do 1. **Never edits code.** It reports. Fixing is `/develop` or `/debug`. 2. **Never marks a criterion met without observing it.** Unobserved is `unverified`, with the reason. 3. **Never hides what it could not check.** The list of unverified criteria goes in the report every time, even when it is long, even when everything else passed. 4. **Never revi