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今天更新