How do I install the Audit Report skill?

Run npx skillmds@latest add edwinhu/audit-report 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 Report 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 Report?

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 Report free to use?

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

Who published Audit Report?

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

Audit Report by edwinhu — Agent Skill

Name: Audit Report
Author: edwinhu

Audit Report

Use when a Bluebook footnote audit's findings need to be turned into a report the user can review before any corrections are applied - 'show me the audit results', 'what did the audit find', 'write up the citation problems', 'give me the report', 'which footnotes are broken', 'summarize the Bluebook errors'. Produces scratch/AUDIT_REPORT.md. NOT for running the checks themselves or applying fixes.

edwinhu 3494ed6 3.0 KB Updated Sep 17, 2026

File contents

Phase 3: Report

Generate a human-readable audit report and present to the user for review before applying corrections.

What This Phase Does

Merge three-layer findings: mechanical + Gemini per-footnote + Claude cross-footnote review (mechanical > Claude > Gemini priority — see audit-check merge rules)
Categorize by issue type and severity
Flag items needing manual review (low-confidence cross-refs, ambiguous citations)
Generate scratch/AUDIT_REPORT.md
Present summary to user

Three-Layer Merge Priority

Mechanical > Claude cross-review > Gemini per-footnote

Mechanical findings (signal italic, terminal periods, Id. chains, small caps patterns) are deterministic and must never be dropped
Claude cross-review adds cross-footnote patterns (supra chains, hereinafter consistency) and filters Gemini false positives
Gemini per-footnote adds individual source type classification and abbreviation checks

Report Structure

# Bluebook Audit Report

## Summary
- Total footnotes: N
- Clean: N (XX%)
- Issues found: N across M footnotes

## Fix Counts by Category
| Category | Count | Auto-fixable |
|----------|-------|-------------|
| Journal name small caps | N | Yes |
| Book title small caps | N | Yes |
| Cross-reference resolution | N | Yes (high confidence) |
| Id. chain errors | N | Partial |
| Signal formatting | N | Yes |
| Terminal periods | N | Yes |
| Typeface errors (other) | N | Manual |

## Issues by Footnote
[sorted by footnote number]

## Items Needing Manual Review
[low-confidence cross-refs, ambiguous citations, judgment calls]

## Correct As-Is (Gemini False Positives)
[Items Gemini flagged but are actually correct, with reasoning]
[Group by source type: SEC releases (roman), exec orders (roman), etc.]
[Reference: audit-patterns.md Source Type Typeface Reference table]

Why "Correct As-Is" Matters

Many Gemini suggestions are wrong — especially for non-standard source types (SEC releases, exec orders, working paper designations). Documenting WHY these are correct:

Prevents re-flagging if someone re-runs the audit
Forces the reviewer to consciously evaluate each judgment call
Creates a record of the source type classification decisions

Gate: Exit Report

This is a user gate. The workflow pauses here.

scratch/AUDIT_REPORT.md exists
User has reviewed the report
User approves proceeding to corrections

Do NOT proceed to corrections without user acknowledgment.

Next Phase

After user approval: Read ${CLAUDE_SKILL_DIR}/../../../../skills/bluebook-audit/skills/audit-correct/SKILL.md and follow its instructions.

---name: audit-reportdescription: Use when a Bluebook footnote audit's findings need to be turned into a report the user can review before any corrections are applied - 'show me the audit results', 'what did the audit find', 'write up the citation problems', 'give me the report', 'which footnotes are broken', 'summarize the Bluebook errors'. Produces scratch/AUDIT_REPORT.md. NOT for running the checks themselves or applying fixes.---# Phase 3: ReportGenerate a human-readable audit report and present to the user for review before applying corrections.## What This Phase Does1. Merge three-layer findings: mechanical + Gemini per-footnote + Claude cross-footnote review (**mechanical > Claude > Gemini priority** — see audit-check merge rules)2. Categorize by issue type and severity3. Flag items needing manual review (low-confidence cross-refs, ambiguous citations)4. Generate `scratch/AUDIT_REPORT.md`5. Present summary to user### Three-Layer Merge Priority**Mechanical > Claude cross-review > Gemini per-footnote**- Mechanical findings (signal italic, terminal periods, Id. chains, small caps patterns) are deterministic and **must never be dropped**- Claude cross-review adds cross-footnote patterns (supra chains, hereinafter consistency) and filters Gemini false positives- Gemini per-footnote adds individual source type classification and abbreviation checks## Report Structure```markdown# Bluebook Audit Report## Summary- Total footnotes: N- Clean: N (XX%)- Issues found: N across M footnotes## Fix Counts by Category| Category | Count | Auto-fixable ||----------|-------|-------------|| Journal name small caps | N | Yes || Book title small caps | N | Yes || Cross-reference resolution | N | Yes (high confidence) || Id. chain errors | N | Partial || Signal formatting | N | Yes || Terminal periods | N | Yes || Typeface errors (other) | N | Manual |## Issues by Footnote[sorted by footnote number]## Items Needing Manual Review[low-confidence cross-refs, ambiguous citations, judgment calls]## Correct As-Is (Gemini False Positives)[Items Gemini flagged but are actually correct, with reasoning][Group by source type: SEC releases (roman), exec orders (roman), etc.][Reference: audit-patterns.md Source Type Typeface Reference table]```### Why "Correct As-Is" MattersMany Gemini suggestions are wrong — especially for non-standard source types (SEC releases, exec orders, working paper designations). Documenting WHY these are correct:1. Prevents re-flagging if someone re-runs the audit2. Forces the reviewer to consciously evaluate each judgment call3. Creates a record of the source type classification decisions## Gate: Exit ReportThis is a **user gate**. The workflow pauses here.- [ ] `scratch/AUDIT_REPORT.md` exists- [ ] User has reviewed the report- [ ] User approves proceeding to corrections**Do NOT proceed to corrections without user acknowledgment.**## Next PhaseAfter user approval:Read `${CLAUDE_SKILL_DIR}/../../../../skills/bluebook-audit/skills/audit-correct/SKILL.md` and follow its instructions.

Frequently asked questions