claude-md-improver_skill

This skill audits and improves CLAUDE.md files across a repo, delivering a quality report and targeted updates upon approval.

Shell
Official

5.4k

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill anthropics/claude-plugins-official --skill claude-md-improver

SKILL.md5.9 KB

Overview

This skill audits and improves CLAUDE.md files across a codebase to ensure Claude Code has optimal project context. It finds all CLAUDE.md variants, evaluates quality against templates and rubrics, and produces a concise quality report. With user approval it applies targeted, minimal updates and shows diffs before editing files.

How this skill works

The skill scans the repository for CLAUDE.md, .claude.local.md, and package-level CLAUDE.md files and ranks each file against a quality checklist (commands, architecture, gotchas, conciseness, currency, actionability). It generates a file-by-file quality report with scores and recommended additions. After the report is shown, it proposes minimal, targeted diffs for each file and asks for approval before applying edits. Edits preserve structure and focus only on practical, actionable content.

When to use it

When you want a full audit of CLAUDE.md files or to measure project context quality.
When requesting CLAUDE.md maintenance or seeking project memory optimization.
After a refactor or monorepo restructure to ensure CLAUDE.md currency.
Before onboarding or handing off a project so Claude has accurate context.
When CI or developer confusion points to missing commands or setup details.

Best practices

Make only targeted additions: commands, gotchas, package relationships, and env requirements.
Keep entries copy-paste ready: executable commands and concise steps.
Document non-obvious patterns and configuration quirks, not generic advice.
Use .claude.local.md for personal overrides and ~/.claude/CLAUDE.md for global defaults.
Always present a quality report and show diffs; preserve existing structure and brevity.

Example use cases

Run an audit to list all CLAUDE.md files and get an average quality score and per-file breakdown.
Generate suggested diffs to add missing build, test, and dev commands for quick fixes.
Consolidate or add package-level CLAUDE.md entries in a monorepo to clarify relationships.
Update CLAUDE.md after a breaking config or environment change so future sessions are accurate.
Add concise gotchas and non-obvious patterns discovered during code review to reduce repeated issues.

FAQ

Yes. It will only apply edits after presenting a quality report and receiving explicit user approval, and it shows diffs for each change.

What kinds of updates will it make?

Targeted, minimal additions: actionable commands, required env vars, package relationships, and short gotchas. It avoids verbose or generic content.