AutoGineer
Generated banner for Claude Md Improver
Generated logo for Claude Md Improver

Claude Md Improver

AnthropicOfficialPublished by Anthropic

  • Skill
  • Review and audit
  • Software development
  • Apache-2.0
  • No issues found
Download ZIP

From the author

Audit and improve CLAUDE.md files in repositories. Use when user asks to check, audit, update, improve, or fix CLAUDE.md files. Scans for all CLAUDE.md files, evaluates quality against templates, outputs quality report, then makes targeted updates. Also use when the user mentions "CLAUDE.md maintenance" or "project memory optimization".
— the description by Anthropic

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

The CLAUDE.md Improver is a specialized utility designed to maintain the quality and relevance of project context files. It scans a repository for CLAUDE.md files, assesses them against a structured quality rubric covering architecture, commands, and patterns, and provides a detailed report. Following user approval, it applies targeted updates to ensure the documentation remains actionable, concise, and accurate for future AI interactions.

What it does

  • Discovers all CLAUDE.md files across a repository, including local and global overrides.
  • Evaluates files based on commands, architecture clarity, patterns, conciseness, and currency.
  • Generates a comprehensive quality report with scores and specific improvement recommendations.
  • Proposes targeted, minimal updates to fill gaps or correct stale information.
  • Applies approved changes directly to the codebase while preserving existing structure.

When to use it

  • When you want to audit the quality of your project's AI context documentation.
  • When you notice that Claude is struggling to understand project-specific commands or patterns.
  • During routine project maintenance to ensure CLAUDE.md files reflect current codebase states.
  • When onboarding a new team member or setting up a new repository for AI-assisted development.

Advantages

  • Ensures AI agents have accurate, up-to-date context for more effective assistance.
  • Standardizes documentation quality across different project modules or monorepos.
  • Reduces hallucination by providing clear, actionable commands and architecture maps.
  • Promotes a clean, concise documentation style that is easy for both humans and AI to read.

Usage examples

“Audit my CLAUDE.md file and suggest improvements.”
The agent scans the file, evaluates it against the quality rubric, and presents a report with a score and specific recommendations for missing sections.
“Perform CLAUDE.md maintenance on this repository.”
The agent identifies all relevant files, assesses their current state, and proposes targeted updates to fix stale commands or clarify architecture.

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/anthropics/claude-md-improver/download

  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip claude-md-improver.zip -d .agents/skills

Documentation by Anthropic

CLAUDE.md Improver

Audit, evaluate, and improve CLAUDE.md files across a codebase to ensure Claude Code has optimal project context.

This skill can write to CLAUDE.md files. After presenting a quality report and getting user approval, it updates CLAUDE.md files with targeted improvements.

Workflow

Phase 1: Discovery

Find all CLAUDE.md files in the repository:

find . -name "CLAUDE.md" -o -name ".claude.md" -o -name ".claude.local.md" 2>/dev/null | head -50

File Types & Locations:

TypeLocationPurpose
Project root./CLAUDE.mdPrimary project context (checked into git, shared with team)
Local overrides./.claude.local.mdPersonal/local settings (gitignored, not shared)
Global defaults~/.claude/CLAUDE.mdUser-wide defaults across all projects
Package-specific./packages/*/CLAUDE.mdModule-level context in monorepos
SubdirectoryAny nested locationFeature/domain-specific context

Note: Claude auto-discovers CLAUDE.md files in parent directories, making monorepo setups work automatically.

Phase 2: Quality Assessment

For each CLAUDE.md file, evaluate against quality criteria. See references/quality-criteria.md for detailed rubrics.

Quick Assessment Checklist:

CriterionWeightCheck
Commands/workflows documentedHighAre build/test/deploy commands present?
Architecture clarityHighCan Claude understand the codebase structure?
Non-obvious patternsMediumAre gotchas and quirks documented?
ConcisenessMediumNo verbose explanations or obvious info?
CurrencyHighDoes it reflect current codebase state?
ActionabilityHighAre instructions executable, not vague?

Quality Scores:

  • A (90-100): Comprehensive, current, actionable

  • B (70-89): Good coverage, minor gaps

  • C (50-69): Basic info, missing key sections

  • D (30-49): Sparse or outdated

  • F (0-29): Missing or severely outdated

Phase 3: Quality Report Output

ALWAYS output the quality report BEFORE making any updates.

Format:

## CLAUDE.md Quality Report

### Summary
- Files found: X
- Average score: X/100
- Files needing update: X

### File-by-File Assessment

#### 1. ./CLAUDE.md (Project Root)
**Score: XX/100 (Grade: X)**

| Criterion | Score | Notes |
|-----------|-------|-------|
| Commands/workflows | X/20 | ... |
| Architecture clarity | X/20 | ... |
| Non-obvious patterns | X/15 | ... |
| Conciseness | X/15 | ... |
| Currency | X/15 | ... |
| Actionability | X/15 | ... |

**Issues:**
- [List specific problems]

**Recommended additions:**
- [List what should be added]

#### 2. ./packages/api/CLAUDE.md (Package-specific)
...
Phase 4: Targeted Updates

After outputting the quality report, ask user for confirmation before updating.

Update Guidelines (Critical):

  1. Propose targeted additions only - Focus on genuinely useful info:

    • Commands or workflows discovered during analysis

    • Gotchas or non-obvious patterns found in code

    • Package relationships that weren't clear

    • Testing approaches that work

    • Configuration quirks

  2. Keep it minimal - Avoid:

    • Restating what's obvious from the code

    • Generic best practices already covered

    • One-off fixes unlikely to recur

    • Verbose explanations when a one-liner suffices

  3. Show diffs - For each change, show:

    • Which CLAUDE.md file to update

    • The specific addition (as a diff or quoted block)

    • Brief explanation of why this helps future sessions

Diff Format:

### Update: ./CLAUDE.md

**Why:** Build command was missing, causing confusion about how to run the project.

```diff
+ ## Quick Start
+
+ ```bash
+ npm install
+ npm run dev  # Start development server on port 3000
+ ```

### Phase 5: Apply Updates

After user approval, apply changes using the Edit tool. Preserve existing content structure.

## Templates

See [references/templates.md](references/templates.md) for CLAUDE.md templates by project type.

## Common Issues to Flag

1. **Stale commands**: Build commands that no longer work
2. **Missing dependencies**: Required tools not mentioned
3. **Outdated architecture**: File structure that's changed
4. **Missing environment setup**: Required env vars or config
5. **Broken test commands**: Test scripts that have changed
6. **Undocumented gotchas**: Non-obvious patterns not captured

## User Tips to Share

When presenting recommendations, remind users:

- **`#` key shortcut**: During a Claude session, press `#` to have Claude auto-incorporate learnings into CLAUDE.md
- **Keep it concise**: CLAUDE.md should be human-readable; dense is better than verbose
- **Actionable commands**: All documented commands should be copy-paste ready
- **Use `.claude.local.md`**: For personal preferences not shared with team (add to `.gitignore`)
- **Global defaults**: Put user-wide preferences in `~/.claude/CLAUDE.md`

## What Makes a Great CLAUDE.md

**Key principles:**
- Concise and human-readable
- Actionable commands that can be copy-pasted
- Project-specific patterns, not generic advice
- Non-obvious gotchas and warnings

**Recommended sections** (use only what's relevant):
- Commands (build, test, dev, lint)
- Architecture (directory structure)
- Key Files (entry points, config)
- Code Style (project conventions)
- Environment (required vars, setup)
- Testing (commands, patterns)
- Gotchas (quirks, common mistakes)
- Workflow (when to do what)

Files

ATTRIBUTION.md

Attribution

This folder is an unmodified copy of the Agent Skill "claude-md-improver", distributed by AutoGineer (https://autogineer.com/agent-skills).

The skill's own files are unmodified copies. AutoGineer is not affiliated with or endorsed by the author or the publisher.

Files added by AutoGineer

  • ATTRIBUTION.md: this file, written by AutoGineer

  • LICENSE: copied from plugins/claude-md-management/LICENSE

Requirements and compatibility

Written for: Claude Code, Claude apps

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Needs: Names Claude Code tools, Needs Node.js

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Published by
Anthropic
Publisher
Anthropic (Official)
Source
anthropics/claude-plugins-official · plugins/claude-md-management/skills/claude-md-improver · commit 0412be7
Licence
Apache License 2.0 (redistribution allowed)
  • LICENSE (added by AutoGineer from plugins/claude-md-management/LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by Anthropic.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download claude-md-improver.zip