メニュー
Audits CLAUDE.md files for conflicts, stale rules, missing sections, and cross-file coherence. Produces a health report with auto-fix suggestions. Use when: 'check claude.md', 'audit CLAUDE.md', 'fix claude.md', 'claude md health'.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/DojoGenesis/mcp --skill claude-md-guardianコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Produces a numbered Architecture Decision Record with context analysis, route comparison, decision rationale, consequences, and propagation checklist. Use when: 'write an ADR', 'architectural decision', 'record a decision', 'ADR for'.
Structured codebase intelligence: directory tree with roles, entry points, dependency graph, test coverage map, and annotated 'here be dragons' warnings.
Runs a convergence gate: counts dirty files, sessions since last convergence, open items, and produces a triage report with RED/YELLOW/GREEN status. Use when: 'converge', 'convergence check', 'drift check', 'am I drifting'.
SOC 職業分類に基づく
SKILL.md を表示中
| name | claude-md-guardian |
| version | 1.0.0 |
| model | sonnet |
| description | Audits CLAUDE.md files for conflicts, stale rules, missing sections, and cross-file coherence. Produces a health report with auto-fix suggestions. Use when: 'check claude.md', 'audit CLAUDE.md', 'fix claude.md', 'claude md health'. |
| triggers | ["check claude.md","audit CLAUDE.md","fix claude.md","claude md health"] |
| category | dojo-craft |
| inputs | [{"name":"context","type":"string","description":"Trigger context — branch merge, onboarding, weekly maintenance, behavior inconsistency, or post-learning","required":false}] |
| outputs | [{"name":"health_report","type":"string","description":"CLAUDE.md health report with severity-classified findings and auto-fix suggestions"}] |
CLAUDE.md is the agent's behavioral contract. When rules drift, conflict, or accumulate without review, agent behavior becomes unpredictable in ways that are almost impossible to debug — because the symptom (agent doing the wrong thing) is far removed from the cause (contradictory rule added three sessions ago).
The guardian treats CLAUDE.md like source code: it requires validation, consistency checks, and protection against unreviewed modification. The difference is that source code fails loudly at compile time. CLAUDE.md fails silently at runtime, in production, usually at the worst moment.
Three failure modes threaten CLAUDE.md health:
Do not use this skill to write new CLAUDE.md rules. Use it to validate existing ones.
Find all behavioral configuration files across the entire hierarchy.
Locations to check:
~/.claude/CLAUDE.md — global rules applied to all projects./CLAUDE.md — project root rules./<subdirectory>/CLAUDE.md — subdirectory-specific overrides./AGENTS.md — cross-tool compatibility file (can contradict CLAUDE.md silently)~/.claude/projects/<project-hash>/CLAUDE.md — project-specific agent memory overlaysUse glob and bash to find all CLAUDE.md and AGENTS.md files recursively. Report the full list before proceeding.
Extract all discrete rules from each file.
A "rule" is any imperative statement: "Always do X", "Never do Y", "Use X instead of Y", "Run X before Z." Section headers and commentary are not rules. Specific, actionable directives are rules.
Normalize the phrasing across files to detect semantic equivalents and contradictions. Two rules that say the same thing in different words are redundancies. Two rules that say opposite things are conflicts.
Tag each rule with:
Detect contradictions between files.
A contradiction is when two rules — from different files in the same hierarchy — give opposing instructions for the same situation.
Examples of contradictions:
For each conflict:
Check rules against current codebase state.
Staleness patterns:
glob and bash.wrangler.toml, settings.json, .env, and config files.go.mod, package.json, and recent commits.For each stale rule:
Check for missing standard sections.
A project-level CLAUDE.md should contain at minimum:
A subdirectory CLAUDE.md that overrides the project CLAUDE.md should clearly mark its overrides.
Report which sections are missing and whether their absence is a risk.
Cross-reference with project metadata files.
Check these for consistency with CLAUDE.md rules:
go.mod — module name, Go version, dependency listpackage.json — project name, scripts, dependenciesMakefile — build targets and commandswrangler.toml / wrangler.jsonc — deployment config.goreleaser.yaml — release binary naming and configIncoherence examples:
make test" but Makefile has no test targetDojoGenesis/mcp but go.mod imports mcp-by-dojo-genesisProduce a health report with severity-classified findings.
Severity levels:
Report format:
# CLAUDE.md Health Report
**Date:** YYYY-MM-DD
**Files audited:** N
**Total rules found:** N
## Summary
- Critical: N
- Warning: N
- Info: N
## Critical Findings
[Each finding with: rule quoted, source file, evidence, recommended fix]
## Warning Findings
[...]
## Info Findings
[...]
## Auto-Fix Candidates
[Findings safe to apply automatically — stale ports, dead paths, obvious redundancies]
## Manual Review Required
[Findings requiring human judgment — intentional overrides, ambiguous intent]
Optionally apply auto-fixes for non-controversial issues.
Auto-fix candidates (safe to apply without confirmation):
Do NOT auto-fix:
Always show the diff before applying and get confirmation for changes outside the auto-fix list.
convergence-checker — Runs the broader convergence gate of which a CLAUDE.md audit is one phaseadr-writer — If a CLAUDE.md conflict reveals an unrecorded architectural decision, write an ADRhooks-reference (system-health plugin) — Configure mechanical protection for CLAUDE.md filesScenario 1: "Agent started ignoring the no-force-push rule after last week's merge." → Guardian discovers that a subdirectory CLAUDE.md added for the CLI repo includes "force push is acceptable for feature branches" — an accidental contradiction with the project-level "never force push to main." Classified CRITICAL. Recommendation: add "OVERRIDE: CLI feature branches only" marker and confirm intent with the team.
Scenario 2: "Weekly CLAUDE.md maintenance before the Era 4 sprint." → Guardian finds: 3 rules referencing port 8080 (correct value is 7340 per settings.json) — WARNING; 2 identical rules in global and project CLAUDE.md — INFO; missing testing gate section in subdirectory CLAUDE.md — INFO. No critical conflicts. Auto-fixes applied for port references after confirmation. Deduplication recommendation noted for manual review.
Scenario 3: "Onboarding a new agent to the Gateway codebase."
→ Guardian audits all three levels of CLAUDE.md. Finds that the gateway subdirectory CLAUDE.md references DojoGenesis/mcp but go.mod still imports the deprecated mcp-by-dojo-genesis path — incoherence warning. Also finds no debugging protocol section in the subdirectory file — completeness gap. Both flagged before the agent is handed any Gateway work.