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