How do I install the Audit Verify skill?

Run npx skillmds@latest add edwinhu/audit-verify in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Audit Verify safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Audit Verify?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Audit Verify free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Audit Verify?

edwinhu (@edwinhu) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Audit Verify by edwinhu — Agent Skill

Name: Audit Verify
Author: edwinhu

Audit Verify

Use immediately after Bluebook corrections have been written into a DOCX, before archiving — 'verify the fixes', 'did the corrections apply', 're-scan the corrected docx', 'check the small caps got fixed', 'confirm the footnotes are clean now', 'run the verify phase'. ALWAYS run this rather than trusting that applied fixes landed; silent fix failures are common.

edwinhu 83b3eb1 2.8 KB Updated Sep 17, 2026

File contents

Phase 5: Verify

Re-scan the corrected DOCX to confirm all fixes were applied and no new issues were introduced.

What This Phase Does

Re-extract all footnotes from the corrected DOCX
Re-run mechanical checks (small caps scanner, signal checker, etc.)
Compare findings against the original audit - all flagged issues should now be clean
Report any remaining issues

Verification Checks

Formatting scanner: Re-run scan_formatting.py --docx corrected.docx - expect 0 findings (or only known false positives like "Institutional Investors" in titles)
Cross-reference check: All [_] placeholders should be resolved
Signal formatting: All signals should be italic
Terminal periods: All footnotes should end with periods
Id. chains: All id. references should have single-source predecessors
Gemini re-audit on fixed footnotes: Re-run gemini_audit.py --subset [all previously flagged FNs] to catch issues introduced by fixes or missed in the initial pass

Re-Scan Catches Real Issues

In the "Other People's Votes" audit, the Gemini re-scan on fixed footnotes caught a Wells Fargo press release title (FN206) that wasn't in the original "judgment call" list — it was in the same footnote as other fixes but wasn't flagged initially. The verify phase is not ceremonial; it finds real issues.

The verify phase MUST re-run the scanner on the corrected DOCX. Skipping verification was the root cause of missing 41 small caps fixes in the original audit.

If the re-scan finds issues, go back to Correct phase. Do NOT proceed to Archive with unresolved issues.

Red Flags

Skipping the re-scan because "all fixes applied" → run the scanner; silent fix failures are common.
Dismissing remaining findings as false positives → investigate each one; some "false positives" are real.
Proceeding to Archive with >0 real issues → fix them first; uncorrected issues persist forever.

Gate: Exit Verify

Before proceeding to Archive phase:

Re-scan completed on corrected DOCX
Zero remaining issues (or all remaining are confirmed false positives)
If issues found: returned to Correct phase and re-verified

Next Phase

Read ${CLAUDE_SKILL_DIR}/../../../../skills/bluebook-audit/skills/audit-archive/SKILL.md and follow its instructions.

---name: audit-verifydescription: Use immediately after Bluebook corrections have been written into a DOCX, before archiving — 'verify the fixes', 'did the corrections apply', 're-scan the corrected docx', 'check the small caps got fixed', 'confirm the footnotes are clean now', 'run the verify phase'. ALWAYS run this rather than trusting that applied fixes landed; silent fix failures are common.---# Phase 5: VerifyRe-scan the corrected DOCX to confirm all fixes were applied and no new issues were introduced.## What This Phase Does1. Re-extract all footnotes from the corrected DOCX2. Re-run mechanical checks (small caps scanner, signal checker, etc.)3. Compare findings against the original audit - all flagged issues should now be clean4. Report any remaining issues## Verification Checks1. **Formatting scanner**: Re-run `scan_formatting.py --docx corrected.docx` - expect 0 findings (or only known false positives like "Institutional Investors" in titles)2. **Cross-reference check**: All `[_]` placeholders should be resolved3. **Signal formatting**: All signals should be italic4. **Terminal periods**: All footnotes should end with periods5. **Id. chains**: All id. references should have single-source predecessors6. **Gemini re-audit on fixed footnotes**: Re-run `gemini_audit.py --subset [all previously flagged FNs]` to catch issues introduced by fixes or missed in the initial pass### Re-Scan Catches Real IssuesIn the "Other People's Votes" audit, the Gemini re-scan on fixed footnotes caught a Wells Fargo press release title (FN206) that wasn't in the original "judgment call" list — it was in the same footnote as other fixes but wasn't flagged initially. The verify phase is not ceremonial; it finds real issues.<EXTREMELY-IMPORTANT>## Iron Law: Re-Scan Is Not OptionalThe verify phase MUST re-run the scanner on the corrected DOCX. Skipping verification was the root cause of missing 41 small caps fixes in the original audit.If the re-scan finds issues, go back to Correct phase. Do NOT proceed to Archive with unresolved issues.</EXTREMELY-IMPORTANT>## Red Flags- Skipping the re-scan because "all fixes applied" → run the scanner; silent fix failures are common.- Dismissing remaining findings as false positives → investigate each one; some "false positives" are real.- Proceeding to Archive with >0 real issues → fix them first; uncorrected issues persist forever.## Gate: Exit VerifyBefore proceeding to Archive phase:- [ ] Re-scan completed on corrected DOCX- [ ] Zero remaining issues (or all remaining are confirmed false positives)- [ ] If issues found: returned to Correct phase and re-verified## Next PhaseRead `${CLAUDE_SKILL_DIR}/../../../../skills/bluebook-audit/skills/audit-archive/SKILL.md` and follow its instructions.

Frequently asked questions