Verification Loop

Verification Loop

What This Skill Owns

• Running a defined 7-phase verification sequence in order
• Reporting structured results (PASS / FAIL / PASS_WITH_WARNINGS)
• Enforcing the failure protocol (fix and re-run from the failing phase)
• Acting as an audit tool for existing unmodified projects (Phase 0 comprehension)

When to Use

• After completing a feature or significant change
• Before creating a PR
• User says "verify this", "verifica", "smoke test", "review this"
• After a refactor, or as part of SDD Verify phase
• User drops a project URL and asks for a codebase review

Phases

1. Build

pnpm build 2>&1 | tail -20
# If fails → STOP, fix before continuing

2. Type Check

# TypeScript
npx tsc --noEmit 2>&1 | head -30
# Python
pyright . 2>&1 | head -30

3. Lint

# JS/TS: pnpm lint, Python: ruff check ., Rust: cargo clippy

4. Test

pnpm test 2>&1 | tail -30

5. Spec Verification

Read spec.md if it exists. For each REQ-F and REQ-NF: verify it's implemented. Mark as ✅ / ❌ / ⚠️.

6. Security Scan

pnpm audit --prod 2>&1 | tail -10
npm audit --omit=dev 2>&1 | tail -10

Manual: no hardcoded secrets, no console.log in prod, input validation at boundaries.

7. Smoke Test

Build and start the server, test each endpoint with curl or equivalent client.

Output

Write a verification report:

• Summary: each phase ✅/❌
• Issues: CRITICAL / WARNING / SUGGESTION
• Verdict: PASS | FAIL | PASS_WITH_WARNINGS

Failure Protocol

Audit Mode

For existing projects (no change to verify), add a Phase 0: Architecture Comprehension before the 7 phases: read the codebase structure, entry points, config, and test suite. Then run all 7 phases and produce a structured audit report.

Pitfalls

• Skipping phases (especially security) — run all 7 in order
• Ignoring test failures — do NOT skip failed tests
• Verifying without the spec — always read spec.md first if it exists
• Trusting npm audit without reviewing critical findings