claude-md-check

To audit a CLAUDE.md orchestrator, validate its role definition, reference patterns, commands, permissions, thin structure, and basic rules against six checks to produce a PASS/WARN/FAIL report with actionable improvements.

A thin orchestrator design delegates tasks to subagents and uses path-based references instead of embedding logic directly. The audit verifies your CLAUDE.md follows this pattern to ensure proper delegation and maintainability.

You check if CLAUDE.md references are path-based by running an audit that validates reference file patterns against examples in references/*.md. The audit confirms references follow proper path conventions and subagents are correctly delegated.

Yes, you can validate CLAUDE.md permissions and role definitions without external dependencies. The auditor evaluates six checks including role definition and permissions natively, producing a pass/fail report with remediation guidance.

The PASS/WARN/FAIL report indicates whether your CLAUDE.md orchestrator meets six structural checks for role definition, references, commands, permissions, thin design, and rules. PASS means compliant, WARN signals partial issues, and FAIL identifies critical gaps requiring actionable improvements.

You should audit your CLAUDE.md orchestrator when subagents are not properly delegated, references are not path-based, or the file structure lacks clear role definitions and permissions. The audit identifies structural weaknesses and provides actionable remediation steps.