anthropics/claude-plugins-official

claude-md-improver

Audit and improve CLAUDE.md files in repositories.

Ver código fuente

Cómo usar

  1. Copia el comando y revisa el paquete antes de instalarlo en tu entorno de agente.
  2. Consulta las herramientas, credenciales y entornos necesarios en el documento original.
  3. Describe las entradas y el resultado deseado; contrasta la salida con las fuentes.
npx skills add https://github.com/anthropics/claude-plugins-official --skill claude-md-improver

Antes de empezar

  • La instalación no incluye suscripción al modelo, cuota API ni permisos sobre tus archivos.
  • Las estrellas e instalaciones reflejan actividad, no una prueba independiente de calidad o seguridad.
Documento original del Skill

Contenido del repositorio de origen con títulos, ejemplos, código, tablas, enlaces e imágenes preservados.

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:

bash
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
  1. 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
  1. 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:

markdown
### Update: ./CLAUDE.md

**Why:** Build command was missing, causing confusion about how to run the project.
  • ## 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 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)

Relacionados por tarea

del mismo repositorio

Más Skills

Todos los Skills
anthropics
Oficial

skill-creator

Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.

Instalaciones / 1h
4
GitHub Stars
47,9 mil
Actualizado
21 nov
anthropics
Oficial

frontend-design

Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.

Instalaciones / 1h
8
GitHub Stars
47,8 mil
Actualizado
20 nov
anthropics
Oficial

build-mcpb

This skill should be used when the user wants to "package an MCP server", "bundle an MCP", "make an MCPB", "ship a local MCP server", "distribute a local MCP", discusses ".mcpb files", mentions bundling a Node or Python runtime with their MCP server, or needs an MCP server that interacts with the local filesystem, desktop apps, or OS and must be installable without the user having Node/Python set up.

Instalaciones / 1h
1
GitHub Stars
47,7 mil
Actualizado
19 nov
anthropics
Oficial

project-artifact

Generate and publish a project status artifact — an opinionated, tabbed status page for a project too big for one update (overview & success criteria, the workstream sequence, next steps, plus background, plan, risks & open questions, and decisions/FAQ when they earn a tab) — published with the built-in Artifact tool to a default-private claude.ai page the user can share with teammates. Use when a piece of work spans several workstreams and you want a shareable overview kept current. Each artifa

Instalaciones / 1h
1
GitHub Stars
47,7 mil
Actualizado
19 nov