verifylisted

# Verify — Pre-Completion Check ## Iron Law NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE. "I tested it" without output is an unverified claim. ## When to Trigger - Before a `/go` subagent reports "done" - Before `/ship` creates a PR - Before telling the user "it's ready" - After any significant code change ## Process ### 1. Build ```bash # Detect and run the project's build command npm run build # or: go build ./... | cargo build | make ``` Must exit 0. If it fails, fix before proceeding. ### 2. Test ```bash # Run the project's test suite npm test # or: go test ./... | pytest | cargo test ``` Must exit 0. If tests fail, invoke `debug` skill. ### 3. Lint ```bash # Run linter if configured npm run lint # or: golangci-lint run | ruff check | cargo clippy ``` Warnings are OK. Errors must be fixed. ### 4. Type Check (if applicable) ```bash npx tsc --noEmit # TypeScript mypy . # Python ``` ### 5. Final Sanity - [ ] No `console.log` / `print` debug statements left - [ ] No `TODO` or `FIXME` introduced without explanation - [ ] No hardcoded test values or credentials - [ ] All new files are tracked by git ## Anti-Rationalization | Excuse | Rebuttal | What to do instead | |--------|----------|-------------------| | "Tests pass locally" | Did you actually run them? Trust the output, not your memory. | Run `npm test` right now. Show the output. | | "I only changed one file" | One file can break the entire build. Imports propagate. | Full build + tes