← ClaudeAtlas

verify-and-reviewlisted

Use before you say that work is done, fixed, or ready for review. Also use it when the user says "make sure it works", "verify this", or "is it ready?". Runs the command or page that the user will use, and reads every count, status line, and exit code. Reviews the whole diff, and labels each claim as measured, inferred, or not verified. This catches a wrong count or a buried warning before handoff. Not for writing or proving tests (use `tests-that-catch-bugs`).
theonly1me/shadowclone · ★ 26 · Code & Development · score 85
Install: claude install-skill theonly1me/shadowclone
# Verify the Real Outcome ## Use when You are about to say that a change is done, fixed, or ready for review. A question does not need this skill. Answer it directly. ## Gates 1. Did you run what the user runs: the command, the page, or the request, on the surface that they use? A passing unit test does not show that the command works. 2. Did you read every line of the real output, including counts, totals, the final lines, and the exit code? Does each one match what happened? 3. If the command writes files, did it run in a temporary home or a copy? Did you read the files that it wrote? 4. Does each claim in your report have a label: measured, inferred, or not verified? 5. Did you read the whole diff, including new files, and remove debug output, temporary mutations, and unrelated edits? 6. Does the report list each behavior choice, such as a skip or a fallback, with its output line? ## Process 1. List what changed for the user: commands, output lines, exit codes, written files, pages, and documents. 2. Run the focused tests, then the required check of the repository. Run a broad check again only when a later change needs it. 3. Run the real command, or open the real page. Use a temporary home folder for a command that writes files. For a page, take a screenshot and look at it. 4. Read the output line by line. Compare each count, status, and path with what you know happened. A wrong count is a bug, even when all tests pass. 5. Do one failure path as well, such as a miss