code-verificationlisted

# Code Verification Skill A systematic post-implementation verification workflow that catches the bugs AI coding assistants most commonly introduce. This is NOT a code review for style or architecture — it is a mechanical correctness checklist that catches structural errors (TDZ, imports, dead code, mock leakage, CSS orphans, React anti-patterns) that humans and AI both miss during implementation. ## When to Use - **After every code change** (1-2 files changed -> run immediately) - **After a multi-file feature** (run on all changed files in one pass) - **After writing/modifying tests** (switch to Test Verification mode) - **Before marking any task complete** (final gate) - **When a subagent completes work** (verify their output) - **When user says**: "verify", "check quality", "audit code", "run verification", "quality gate", "pre-commit check" ## Quick Start ``` 1. Identify changed files (git diff --name-only or manual list) 2. Run the 7-category checklist below on each file 3. Run automated checks (build, lint, tests) 4. Report findings as PASS / FAIL / WARNING 5. Fix all FAIL items before proceeding ``` --- ## The 7-Category Verification Checklist ### Category 1: Variable Declaration Order (TDZ Prevention) **What to check:** Variables, constants, and hooks used BEFORE their declaration in the same scope. **How it breaks:** JavaScript `const` and `let` have a "temporal dead zone" — referencing them before their declaration line throws `ReferenceError` at runtime,