Claude Md Improver

作者 anthropicsb78ac49cdc6b无许可证37K 个星标收录于 2026年10月8日更新于 2026年10月8日仓库今天更新

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".

精选仅含说明AI & Agents
AI 生成的概览

审查仓库中的 CLAUDE.md 文件,评估其质量,并在获得批准后应用有针对性的改进。

功能
该技能会在仓库中查找所有 CLAUDE.md 文件,包括项目根目录、本地覆盖、全局、包级以及嵌套位置。它依据文档化的命令、架构清晰度、非显而易见的模式、简洁性、时效性和可执行性等加权标准评估每个文件,并给出分数和等级。随后输出逐文件的质量报告,列出问题和建议补充内容,并在用户批准后应用有针对性的修改,展示差异并说明每项改动的原因。
适用场景
当用户要求检查、审查、更新、改进或修复 CLAUDE.md 文件时使用,也适用于用户提到 CLAUDE.md 维护或项目记忆优化的情况。它适合 Claude Code 项目上下文可能过时、不完整或缺少关键命令和注意事项的仓库。
运行要求
仅以指令形式运行,不附带脚本。它依赖智能体的 Read、Glob、Grep、Bash 和 Edit 工具,并在用户批准后写入 CLAUDE.md 文件。

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 [blocked] 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:

markdown
### 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 work2. **Missing dependencies**: Required tools not mentioned3. **Outdated architecture**: File structure that's changed4. **Missing environment setup**: Required env vars or config5. **Broken test commands**: Test scripts that have changed6. **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)

来源与署名

来源:anthropics/claude-plugins-official位于plugins/claude-md-management/skills/claude-md-improver提交b78ac49

许可证: 无许可证

内容归原作者所有。SourceWeft 从公开仓库中收录这些内容。

举报或申请下架

更多来自 anthropics/claude-plugins-official 的技能

Skill Development

anthropics

精选

指导创建 Claude Code 插件技能,涵盖结构、描述、渐进式披露与验证。

AI & Agents37K今天更新

Plugin Structure

anthropics

精选

指导 Claude Code 插件的结构、清单与组件布局。

AI & Agents37K今天更新

Project Artifact

anthropics

精选

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 artifact is backed by a small per-project config in the plugin data dir, so refreshing it re-gathers live state, redeploys the same URL, and reports only the delta. For software projects whose workstreams are PRs, also read swe.md (the X.Y PR-numbering convention; pulling PR state with gh/git; a per-PR detail block). Needs the built-in Artifact tool (claude.ai login). Not for single-PR changes or public docs.

待分类37K今天更新

Command Development

anthropics

精选

指导创建 Claude Code 斜杠命令,涵盖结构、YAML frontmatter、参数与插件功能。

AI & Agents37K今天更新

Playground

anthropics

精选

构建自包含的交互式 HTML 演练场,包含控件、实时预览和可复制的提示词输出。

Design & Creative37K今天更新

M5 Onboard

anthropics

精选

通过 USB 检测 M5Stack ESP32 开发板,刷写 UIFlow 2.0 固件并安装 MicroPython 应用包。

DevOps & Cloud37K今天更新