claude-md-guardian

Audits CLAUDE.md files for conflicts, redundancies, and stale rules.

2|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/DojoGenesis/gateway --skill claude-md-guardian
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: claude-md-guardian
Source: https://github.com/DojoGenesis/gateway/tree/main/plugins/system-health/skills/claude-md-guardian
Command: npx skills add https://github.com/DojoGenesis/gateway --skill claude-md-guardian

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Agents rely on the CLAUDE.md contract for consistent behavior. Over time rules can drift, conflict, or become obsolete, leading to unpredictable actions. This skill audits CLAUDE.md files to surface those issues and optionally enforces protection hooks.

Core Features & Use Cases

  • Inventory & Normalize: Collects all global, project, and sub‑directory CLAUDE.md files and extracts discrete rules.
  • Conflict & Redundancy Detection: Identifies contradictory, duplicated, or deprecated rules across the hierarchy.
  • Staleness Analysis: Flags rules that reference removed tools, paths, or patterns.
  • Protective Hook Installation: Optionally creates a PreToolUse hook that blocks unauthorized CLAUDE.md edits.
  • Actionable Report: Generates a health report with counts, conflict details, redundancy listings, and remediation suggestions.
  • Use Cases: Run after a branch merge that touched CLAUDE.md, during weekly maintenance, when onboarding new agents, or after a reflect‑and‑learn session.

Quick Start

Ask the CLAUDE.md Guardian to generate a health report for the repository.

Frequently Asked Questions about claude-md-guardian

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit a CLAUDE.md file for conflicting or stale rules?

Auditing CLAUDE.md files for stale rules involves collecting all global, project, and sub-directory files to extract discrete rules, then generating a health report that identifies conflicts, redundancies, and deprecated references.

Why does my agent behave unpredictably after a branch merge that touched CLAUDE.md?

Unpredictable agent behavior after a branch merge often stems from CLAUDE.md rule drift, conflicts, or obsolete instructions. Auditing the files extracts discrete rules and generates a health report detailing these exact issues.

Can I block unauthorized edits to CLAUDE.md files automatically?

You can block unauthorized edits to CLAUDE.md files by optionally installing a PreToolUse hook. This protective mechanism enforces file governance and prevents unauthorized modifications to the agent behavior contract.

What is CLAUDE.md staleness analysis and when do I need it?

CLAUDE.md staleness analysis identifies and flags rules that reference removed tools, paths, or patterns. You need this during weekly maintenance, after branch merges, or when onboarding new agents to ensure rules remain accurate.

Does the CLAUDE.md audit require file system access?

The CLAUDE.md audit requires file system access to read global, project, and sub-directory files. This access is necessary to inventory rules, detect conflicts, and optionally configure the PreToolUse protection hook.