Claude Md Improver

secondsky/sap-skills/.agents/skills/claude-md-improver

作者 secondsky652a861d3ed422b71f01c8805f9ec03b14017cd8無授權條款收錄於 2026年10月9日更新於 2026年10月9日

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 維護、專案記憶最佳化時使用。它適合專案情境檔案可能過時、不完整或缺少關鍵指令與設定說明的儲存庫。
執行需求
僅包含指令，沒有隨附指令碼。它依賴代理的 Read、Glob、Grep、Bash 與 Edit 工具；Bash 用於尋找檔案，Edit 用於套用已核准的修改。不需要憑證或網路存取。

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)
## Related Skills
- **dependency-upgrade**: Include dependency hardening policies and lockfile/security workflow guidance when improving repository CLAUDE.md files

來源與署名

來源：secondsky/sap-skills位於.agents/skills/claude-md-improver提交652a861

授權條款： 無授權條款

內容歸原作者所有。SourceWeft 從公開儲存庫中收錄這些內容。

檢舉或申請下架

更多來自 secondsky/sap-skills 的技能

Sap Sac Scripting

secondsky

指導撰寫、偵錯與最佳化 SAP Analytics Cloud 指令碼，適用於 Analytics Designer 與最佳化故事體驗。

包含腳本
Software Development2026年10月9日

Sap Sac Planning

secondsky

用於設計與偵錯 SAP Analytics Cloud 規劃模型、資料動作與規劃工作流程的指引。

Business & Finance2026年10月9日

Sap Sqlscript

secondsky

指導撰寫、最佳化與偵錯 SAP HANA SQLScript 程序、函式、游標、例外處理常式及 AMDP 方法。

Software Development2026年10月9日

Sap Hana Ml

secondsky

指導使用 SAP HANA 的 hana-ml Python 用戶端進行資料庫內機器學習開發，涵蓋 PAL/APL 演算法、DataFrame、AutoML 與模型儲存。

Software Development2026年10月9日

Sap Btp Master Data Integration

secondsky

指導在 SAP BTP 上設定與整合 SAP 主資料整合服務，涵蓋租用戶、用戶端、散佈模型與 SOAP API。

DevOps & Cloud2026年10月9日

Sap Fiori Tools

secondsky

指導使用 SAP Fiori tools 開發 SAP Fiori 應用程式，涵蓋產生、頁面編輯、註解、預覽與部署。

Software Development2026年10月9日

更多AI & Agents技能

Discernment Nudge

anthropics

精選

在實質回答後附加 2-3 個具體追問，協助使用者查核事實、推理與缺少的背景。

AI & Agents180K今天更新

Ppt Template Creator

anthropics

精選

將使用者的 PowerPoint 範本轉換為可重用的技能，用來產生品牌簡報。

AI & Agents39K2 週前更新

Skill Development

anthropics

精選

指導建立 Claude Code 外掛技能，涵蓋結構、描述、漸進式揭露與驗證。

AI & Agents37K今天更新

Plugin Structure

anthropics

精選

說明 Claude Code 外掛的結構、資訊清單與元件配置方式。

AI & Agents37K今天更新

Command Development

anthropics

精選

指導建立 Claude Code 斜線命令，涵蓋結構、YAML frontmatter、參數與外掛功能。

AI & Agents37K今天更新

Claude Md Improver

anthropics

精選

稽核儲存庫中的 CLAUDE.md 檔案、評估其品質，並在取得核准後套用針對性的改進。

AI & Agents37K今天更新