claude-md

Validate CLAUDE.md changes by running a gate-driven audit that checks proposed edits for placement, redundancy, and universality. The validation outputs a structured ADD, REDIRECT, or SKIP action with exact markdown for safe application.

A CLAUDE.md drift scan compares proposed content against existing .claude/rules/*.md files. It surfaces misrouted content and orphan rules, ensuring updates do not create redundant or conflicting instructions across your configuration files.

Prevent bloated rules and misrouted content in CLAUDE.md by applying a gatekeeper validation step before editing. This audit checks content universality and routing, redirecting misplaced entries to .claude/rules/*.md instead of allowing bloat.

Yes, the CLAUDE.md validation gate explicitly audits .claude/rules/*.md files. It performs a drift scan against them to catch misplacements and orphan content, ensuring correct routing between the main file and specific rule files.

The best way to structure CLAUDE.md updates for automation is to supply proposed changes to a validation gate. The gate outputs exact markdown with an ADD, REDIRECT, or SKIP directive, allowing downstream tools to apply changes automatically.

You should skip adding new content to CLAUDE.md when the validation gate determines the proposed change lacks universality or is redundant. The gate outputs a SKIP action if the content is too specific or already exists in .claude/rules/*.md.