claude-md-improver

Audit and improve CLAUDE.md files against quality rubrics and templates.

16|1|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/SocialGouv/iterion --skill claude-md-improver-socialgouv
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: claude-md-improver
Source: https://github.com/SocialGouv/iterion/tree/main/vendor/github.com/SocialGouv/claw-code-go/internal/tools/bundled_skills/claude-md-management/skills/claude-md-improver
Command: npx skills add https://github.com/SocialGouv/iterion --skill claude-md-improver-socialgouv

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? CLAUDE.md files often become stale, sparse, or filled with generic advice, leaving Claude Code without accurate project context and forcing repeated rediscovery of commands, architecture, and gotchas. ## Core Features & Use Cases - Repository-wide discovery: Scans for all CLAUDE.md, .claude.md, and .claude.local.md files across project roots, packages, and nested directories. - Scored quality assessment: Evaluates each file against a six-criterion rubric (commands, architecture, patterns, conciseness, currency, actionability) and outputs a graded report before any changes. - Targeted updates with diffs: Proposes minimal, project-specific additions shown as diffs, then applies them with the Edit tool after user approval. - Use Case: After a major refactor, run an audit to find that build commands in the root CLAUDE.md no longer work, get a scored report, and apply corrected commands plus newly discovered testing gotchas. ## Quick Start Audit all CLAUDE.md files in this repository, give me a quality report, and propose targeted improvements.

Frequently Asked Questions about claude-md-improver

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

FAQPage Schema
How do I audit CLAUDE.md files in my repository?▼

Run the skill to scan for all CLAUDE.md, .claude.md, and .claude.local.md files, then receive a scored quality report per file. It evaluates commands, architecture clarity, patterns, conciseness, currency, and actionability before suggesting any changes.

What makes a good CLAUDE.md file for Claude Code?▼

A good CLAUDE.md is concise, contains copy-paste-ready commands, documents project-specific architecture and gotchas, and reflects the current codebase. It should avoid generic best practices and restating information obvious from the code itself.

Does the skill update CLAUDE.md files automatically?▼

No. It always outputs a quality report first, then asks for user confirmation before applying updates. Proposed changes are shown as diffs with explanations of why each addition helps future sessions.

Can I use different CLAUDE.md files in a monorepo?▼

Yes. Claude auto-discovers CLAUDE.md files in parent directories, so package-level files in packages/* work alongside the root file. The skill audits each file separately and flags duplicate information across them.

What should not be added to a CLAUDE.md file?▼

Avoid obvious code descriptions, generic best practices, one-off bug fixes, and verbose explanations. Every line should be project-specific, current, and useful enough to justify its place in the context window.