What problem does it solve?
Diagnose public guideline files (Track A: root AGENTS.md + Claude bridge; Track B: root CLAUDE.md) against best-practice benchmarks, report issues, and obtain user consent before optional improvements. The track is auto-detected from the existence of root files and the report header shows Detected track: X. It performs anti-pattern checks (e.g., vague advice, linter overlaps, content that reads like code, outdated references, cross-tool duplication, leakage of private settings), token efficiency checks, structure checks, and reference path validation, offering migration options when both tracks exist.
Core Features & Use Cases
- Auto-detects the active track from root files (AGENTS.md / CLAUDE.md) and validates associated bridges.
- Performs anti-pattern detection, references validation, token-efficiency checks, and boundary/structure analysis.
- Suggests track migrations to consolidate rules into a single track when both exist.
- Produces a guided diagnostic report with actionable recommendations and a user-consent workflow.
Quick Start
Run the audit to generate a diagnostic report for AGENTS.md and CLAUDE.md.