| name | audit-pass2-verifier |
| description | Read an audit report claiming fixes applied (PASS 2, PASS 3, etc), verify each claim against source code, then execute deferred items. Use when handed an audit markdown that lists "FIX: applied" entries, when asked to "close audit findings", or to "validate audit work to production". |
audit-pass2-verifier
Trigger
User hands you (or you find) an audit/review markdown that:
- Tables findings with severity (CRITICAL/HIGH/MEDIUM/LOW)
- Marks some as
FIX: applied in PASS N
- Marks others as
DEFERRED
- Includes file paths + line numbers
User says: "verify the audit", "close the audit", "complete the deferred items", "drive this to production-validated".
The Rule
Audit docs lie. Verify every "FIX applied" claim in source before trusting. Then execute deferred items in priority order.
Why: Audit markdown is human/agent-authored. Edits get reverted, hooks reformat them away, parallel sessions overwrite them. Trusting the doc without verification = building on quicksand.
How to apply: Source-of-truth pass, then deferred-execution pass, then test-suite delta.
Workflow
Step 1 — Read audit doc ONCE
Capture: findings table, status column, file paths, line numbers. Do NOT re-read.
Step 2 — Verify each "applied" claim
For each PASS N "FIX: applied" entry:
grep -n "<expected-symbol>" <file-path>
Use grep -n not rg when pattern has special chars (parens, backslashes) — shell escape eats \( in unquoted rg patterns and silently returns 0 matches. Match: claim verified. No match: doc lied or work got reverted.
Build a verification table:
