audit-claude-md

Rewrites CLAUDE.md into terse imperative rules and moves rule-shaped content to .claude/rules/ or .claude/hooks/.

Updated Sep 3, 2026
One-click install
npx skills add https://github.com/CMiller838/meal-planner --skill audit-claude-md-cmiller838
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit-claude-md
Source: https://github.com/CMiller838/meal-planner/tree/main/.claude/skills/audit-claude-md
Command: npx skills add https://github.com/CMiller838/meal-planner --skill audit-claude-md-cmiller838

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? CLAUDE.md files tend to accumulate narrative history, duplicated rules, and stale notes until they become bloated and hard for agents to follow. This Skill audits the file, cuts it down to single-line imperative rules under 200 lines, and relocates anything that belongs in .claude/rules/ or .claude/hooks/. ## Core Features & Use Cases - Content classification: Sorts every section of CLAUDE.md into history/narrative, standing rules, enforceable behaviors, stale notes, and keep-worthy facts, then handles each class appropriately. - Rule extraction: Moves path-scoped or language-specific rules into .claude/rules/*.md files with YAML paths frontmatter, and flags mechanically checkable behaviors as hook candidates without building them unasked. - Use Case: Your project's CLAUDE.md has grown to 600 lines of changelog prose and mixed conventions. Run this Skill to compress it into grouped imperative sections, move Python-specific rules into .claude/rules/, and get a diff summary of what was cut or relocated. ## Quick Start Ask the agent to audit and tighten the project's CLAUDE.md, moving rule-shaped content into .claude/rules/ and reporting what changed.

Frequently Asked Questions about audit-claude-md

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

FAQPage Schema
How do I reduce the size of my CLAUDE.md file?

Audit each section and classify it as history, standing rule, enforceable behavior, stale note, or essential fact. Delete changelog prose, compress facts to one imperative line each, and move path-scoped rules into .claude/rules/ files, targeting under 200 lines total.

What content should move from CLAUDE.md to .claude/rules/?

Move any standing rule that is language-specific or path-scoped, such as Python docstring conventions, into a .claude/rules/*.md file with YAML paths frontmatter. Globally applicable rules stay in CLAUDE.md as single imperative lines.

When should CLAUDE.md content become a hook instead of a rule?

Content describing automated, mechanically checkable behavior like lint-on-save or blocking dangerous commands is a hook candidate. The Skill flags these in its report rather than building them, so you decide whether to implement them in .claude/hooks/.

Does the audit delete content permanently?

History and narrative sections are deleted because git log and docs/ files like PLAN.md and ARCHITECTURE.md remain the source of truth. The final report names where everything went: deleted, moved to docs/, or moved to .claude/rules/.

What are the limitations of auditing CLAUDE.md automatically?

The audit does not create hooks unasked; it only flags candidates. It also requires reading existing .claude/rules/ and .claude/hooks/ first to avoid duplicating rules, and stale notes must be verified against referenced files before deletion.