Verification Before Completion

Verification Before Completion

A discipline, not a phase: never assert that something works until you have run the command that proves it and read the output — in this session, just now. Claiming work is complete without verification is dishonesty, not efficiency.

⛔ The Iron Law

No completion claim without fresh verification evidence.

If you haven't run the proving command in this exchange, you cannot claim it passes. "Should pass", "looks right", and "I changed it the way they asked" are predictions, not evidence.

The Gate Function

Before any completion claim, walk these five steps in order:

1. IDENTIFY — What single command (or observation) would prove this claim? ("The tests pass" → pytest. "The build works" → the build command. "The bug is fixed" → the failing repro now succeeds.)
2. RUN — Execute the full command, fresh and complete. Not a subset, not a remembered result from earlier, not CI from yesterday.
3. READ — Read the entire output. Check the exit code. Count the failures. Don't skim for green and stop.
4. VERIFY — Does the output actually confirm the claim? A passing exit code on the wrong command proves nothing.
5. CLAIM — Only now state the result, and state it precisely ("142 passed, 0 failed" beats "tests pass").

Skipping any step turns a verification into a guess.

What counts as a claim

Any of these is a completion claim and triggers the gate:

• "Done", "finished", "complete", "ready"
• "It works", "this fixes it", "the bug is gone"
• "Tests pass", "the build is green", "no errors"
• About to commit, push, open/merge a PR, or deploy
• Reporting that a sub-task or delegated agent succeeded

What counts as evidence

• A command you ran in this session, with its output visible.
• The exit code (a command can print reassuring text and still exit non-zero).
• The relevant slice of output read in full (the failure count, not just the last line).

NOT evidence: a previous run, a CI result you didn't open, a teammate's report you didn't confirm, or your own expectation of what the code does.

The tests aren't the only gate

Tests prove behavior; they don't prove the change is clean. When the project configures static gates — a type checker (tsc --noEmit, mypy), a linter (eslint, ruff), a dead-code / unused-export check (knip, vulture) — those are part of "done" too. A change is not complete until they run green this session, on the same five-step gate (IDENTIFY → RUN → READ → VERIFY → CLAIM).

The failure mode this prevents is a rotted gate: a repo declares mypy strict = true (or eslint --max-warnings 0) and it quietly sits on 40+ errors because no one runs it — so the gate that was supposed to stop any-casts, stale type: ignores, and dead exports stops nothing. A declared strict gate with N errors is not "passing"; it is broken, and adding to it is adding slop the gate was meant to catch. Run it, read the count, and either land it at zero or name the pre-existing debt explicitly — never let "the tests pass" stand in for "the gates pass."

The docs are part of the surface you changed

Tests prove behavior, the static gates prove the code is clean — neither notices that the README still documents the flag you just renamed. A change carries a documented surface when it adds, renames, or removes something a person types, configures, or calls: a CLI flag, env var, config key, endpoint, command, script, package or directory, install/setup step, or public exported symbol. A purely internal refactor usually carries none — say so and move on. This gate is for changes that made an existing document wrong.

Same five steps, with a grep as the proving command:

1. Derive the identifiers your diff touched — the old names as well as the new ones. The old name is what the docs still contain.
2. Grep the doc set for them: README, docs/, and inline docs.
3. Read the hits, in place. A hit is not automatically drift; the surrounding sentence decides.
4. Reconcile or report. Fix what your change made wrong, or state plainly which docs are stale and why you're leaving them.

Two things make this gate miss:

• Prose survives; inventories rot. People reread the paragraph they're editing and never reread the table three sections down. Endpoint tables, architecture diagrams, project-layout blocks, ADR indexes, and command lists go stale first and silently — check those before the prose.
• An empty grep is not evidence of no drift. Docs use shorthand, globs, and brace expansion (/api/{users,orders}), so a literal grep for orders can miss a line that documents it. When the doc plausibly covers the area, open the section and read it rather than trusting a clean grep.

Scope this to reconciliation, not authoring: it touches documents that already reference what you changed. It never means writing new docs nobody asked for — that produces the doc-slop project-documentation exists to prevent.

What you're about to publish

Committing publishes. The tests prove the code runs and the doc gate proves the docs still match — neither notices that the diff also carries a real customer's email, or a comment citing "Phase 3" of a plan that exists only in this session's context. Both are invisible to every other gate and permanent once pushed.

This is not a gate on committing. It reports; the user decides. Refusing to commit doesn't prevent a leak — the commit happens without you — it just removes the one reader who noticed. Your job is that the check ran and the finding is on the record, in the same response, not that the commit was stopped.

Not blocking is not the same as not urgent. Proportionality governs how much room a finding takes up, never how plainly you state what it costs — the worst outcome here is a hedged sentence about a live credential, which reads as diligence and functions as silence.

Read git diff --staged and look for three things at once. It's a scan, not three passes, and it costs seconds:

1. Who is in this diff? Real people or real credentials — in data files, fixtures, seeds, configs/env, logs, captured output, or a doc pasting a "real" example.

   Look up what this project already decided before reasoning from general privacy principle: CLAUDE.md and project instructions, memory, .gitignored paths, and the convention the repo's other fixtures follow. That's the answer when it exists, and it beats anything you'd derive. Exit condition: "This repo declares <X> protected" — or "nothing is declared; the other fixtures use synthetic values, so I've matched them."

   A staged credential is already compromised. An API key, token, private key, password, or connection string that reached a file you staged must be treated as burned — it has been on disk, in your shell history, and in whatever tooling watched the working tree. Say that plainly and name rotation, not deletion, as the fix; dropping the line from the diff leaves a live secret that someone already had. Don't hedge it into a conditional — "if nothing was pushed you can probably skip rotation" is the sentence that gets a key left valid. Route the durable fix to configuration-strategy.

   For personal data, name what's exposed and offer redaction or synthetic values (test-data-strategy); for internal-but-not-personal — hostnames, client names, paths with usernames — one line is the right size. Full ladder in references/pre-commit-gate.md § Leg 1.

2. Would a stranger understand this? Internal identifiers in staged content: Phase 2, CP1.3, T02, finding #17, checkpoint 3/5. Check, don't assume — git ls-files '*.md' | xargs grep -l "<term>". Anchored in a tracked document, it's a real cross-reference; unanchored, it's a private label a reader can't resolve, so write the meaning instead. Rewrites in § Leg 2.

3. Does this comment belong in the code? New comment blocks of four or more lines: system-level rationale belongs in an ADR with the comment carrying a pointer; a local invariant the types can't express stays inline. Calibration in § Leg 3.

Exit condition — one line in the response where you commit, then keep going. It reports what you found, and it scales to that:

• Nothing found → "Staged diff checked, nothing to flag." That is the entire line. Do not list the categories you scanned. "No personal data, no unanchored references" on a diff that was never going to contain either teaches the reader nothing, and asserting a category is clean is not the same as having had a reason to raise it.
• Something found → name only that, and what you did about it: "Staged diff: fixtures/accounts.json carries 40 real-looking email addresses — replaced them with synthetic values."

A clean diff ends here. Don't narrate the scan, don't open with "not yet", don't ask permission to proceed, and don't open the reference file — a clean scan needs none of it. A gate that makes every commit feel expensive is one that gets routed around, and then it protects nothing.

If the diff has code hunks and something tripped, invoke code-reviewing and let it work the diff — it owns the repo-wide greps and the slop catalog, and it is almost never reached at commit time on its own. A docs- or config-only diff never routes there.

One handling rule that applies while checking, not after: never echo a real secret or a real person's data into context to inspect it. Match on shape and location, report the file and line, and let the user decide. Pasting the value to prove it's there is the leak.

What you write into a doc is also a claim

A document is a set of assertions about the code, and the Iron Law does not stop at prose. Every factual sentence you add must come from something you read this session, not from what you remember the code doing. Sweeps introduce errors as readily as they remove them, and a confidently-worded wrong sentence outlives the stale one it replaced.

• Enumerate from the source of truth. Endpoints come from the router file, scripts from listing the directory, packages from the manifest, flags from the arg parser. Do not reconstruct a list from memory and then spot-check it.
• Re-read your own doc diff before committing, against the code — the same scrutiny you would give a code hunk. This is where a wrong claim gets caught.
• Verify links resolve. A doc edit that moves or adds a relative link is a change whose proving command is a link check.

Rationalizations to reject

Red flags — stop and verify first

• You're typing "done" / "fixed" / "works" without a command output above it.
• You feel satisfaction ("Great!", "Perfect!") before running anything.
• You're about to commit/push/PR and haven't run the test command this session.
• You ran the tests but not the configured type checker / linter the repo defines.
• You're relying on a partial run or a stale result.
• You renamed or removed something a user types or configures, and haven't grepped the docs for the old name.
• You're writing a sentence about how the code behaves into a doc, and you haven't opened that code this session.
• You're about to commit and haven't read git diff --staged — you're committing what you believe you staged.
• The diff touches a fixture, seed, log, capture, or .env-shaped file and nobody has said what's protected in this project.
• You're writing a plan's vocabulary — a phase, checkpoint, task code, or finding number — into a commit message, comment, or doc, and the plan is not a tracked file.
• You just wrote a comment longer than the code it sits above.
• You're asking permission, or opening with "not yet", on a diff you have already concluded is clean.
• You're about to refuse a commit rather than report what you found and let the user choose.

Cross-Skill References

This skill is the shared "done" gate for every workflow that ends in a claim:

• tdd-workflow — the GREEN step is a verification: watch the test pass for real
• bug-investigating — confirm the reproducing test now passes before claiming the fix
• deployment-checklist — every checked box is an instance of this gate
• code-reviewing — verify the change before approving, not from the diff alone; also where the publish gate routes a tripped code diff
• code-slop-cleanup — the slop catalog behind the comment-placement check
• git-workflow — writes the commit this gate clears
• project-documentation — establishes which docs are versioned, which the anchor check reads as its baseline
• cicd-pipeline — the pipeline automates this gate; locally, run it yourself first
• project-documentation — the sync sweep and the accuracy method, when the grep turns up docs that need reconciling