From mercury
Compare two Mercury audit reports to show what was fixed, what regressed, and what is new since the last run. Use when the user wants to track audit progress between code iterations, sprints, or refactors.
How this skill is triggered — by the user, by Claude, or both
Slash command
/mercury:mercury-diffThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Diffs two `mercury_*_report.md` files and shows what changed.
Diffs two mercury_*_report.md files and shows what changed.
Accept either:
/mercury-diff report_v1.md report_v2.mdmercury_*_report.md files by mtime:
find "<dir>" -name "mercury_*_report.md" -printf "%T@ %p\n" | sort -n | tail -2
/mercury-audit again.Extract the JSON findings blocks from each report. For each finding use (file + symbol + category) as the key.
## Mercury Diff — <label>
Old: <old report filename> (<date>)
New: <new report filename> (<date>)
### ✅ Fixed (N)
| Sev | Category | File | Symbol | Issue |
...
### 🆕 New Issues (N)
| Sev | Category | File | Symbol | Issue |
...
### ⬆️ Regressions (N)
| Old Sev → New Sev | Category | File | Issue |
...
### Net change: -N critical, -N high, +N medium
/mercury-diff [old_report.md] [new_report.md]
/mercury-diff [project_dir] # auto-picks last two reports
Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.
npx claudepluginhub mli-corp/mercury-audit --plugin mercury