Verification Skill

Verification Phases

Execute verification in this exact order:

1. •

   Build Check

   • •Run the build command for this project
   • •If it fails, report errors and STOP
2. •

   Type Check

   • •Run type checker
   • •Report all errors with file:line
3. •

   Lint Check

   • •Run linter
   • •Report errors
4. •

   Test Suite

   • •Run all tests
   • •Report pass/fail count
   • •Report coverage percentage
5. •

   Console.log Audit

   • •Search for console.log in source files
   • •Report locations

Output Format

After running all phases, produce a verification report:

VERIFICATION REPORT
==================

Build:     [PASS/FAIL]
Types:     [PASS/FAIL] (X errors)
Lint:      [PASS/FAIL] (X warnings)
Tests:     [PASS/FAIL] (X/Y passed, Z% coverage)
Security:  [PASS/FAIL] (X issues)
Diff:      [X files changed]

Overall:   [READY/NOT READY] for PR

Issues to Fix:
1. ...
2. ...

Continuous Mode

For long sessions, run verification every 15 minutes or after major changes:

Set a mental checkpoint:

- After completing each function
- After finishing a component
- Before moving to next task

Run: /verification

Arguments

$ARGUMENTS can be:

• •quick - Only build + types
• •full - All checks (default)
• •pre-commit - Checks relevant for commits
• •pre-pr - Full checks plus security scan