secondsky/sap-skills

claude-md-improver

Audit and improve CLAUDE.md files in repositories.

Voir la source

Mode d’emploi

  1. Copiez la commande et examinez le paquet avant de l’installer dans votre environnement agent.
  2. Consultez le document original pour les outils, identifiants et environnements requis.
  3. Décrivez les entrées et le livrable souhaité ; comparez la sortie aux sources.
npx skills add https://github.com/secondsky/sap-skills --skill claude-md-improver

Avant de commencer

  • L’installation n’inclut ni abonnement au modèle, ni quota API, ni accès aux fichiers.
  • Étoiles et installations reflètent l’activité, pas un test indépendant de qualité ou de sécurité.
Document Skill original

Rendu depuis le dépôt source en conservant titres, exemples, code, tableaux, liens et images.

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)

Related Skills

  • dependency-upgrade: Include dependency hardening policies and lockfile/security workflow guidance when improving repository CLAUDE.md files

Tâches connexes

du même dépôt

Autres Skills

Tous les Skills
secondsky
Communauté

sap-hana-cli

Assists with SAP HANA Developer CLI (hana-cli) for database development and administration. Use when: installing hana-cli, connecting to SAP HANA databases, inspecting database objects (tables, views, procedures, functions), managing HDI containers, executing SQL queries, converting metadata to CDS/EDMX/OpenAPI formats, managing SAP HANA Cloud instances, working with BTP CLI integration, or troubleshooting hana-cli commands. Covers: 91 commands, 17+ output formats, HDI container management, clou

Installations / 1h
1
GitHub Stars
501
Mis à jour
13 nov.
secondsky
Communauté

sap-sqlscript

This skill should be used when the user asks to "write a SQLScript procedure", "create HANA stored procedure", "implement AMDP method", "optimize SQLScript performance", "handle SQLScript exceptions", "debug HANA procedure", "create table function", "inspect a browser-based Datasphere SQL editor with Microsoft Edge CDP", or mentions SQLScript, SAP HANA procedures, AMDP, EXIT HANDLER, or code-to-data paradigm. Comprehensive SQLScript development guidance for SAP HANA database programming includin

Installations / 1h
1
GitHub Stars
501
Mis à jour
13 nov.
secondsky
Communauté

sap-sac-planning

SAP Analytics Cloud (SAC) planning guidance for planning models, planning-enabled stories, data actions, multi actions, version management, data locking, calendar/input workflows, allocations, value driver trees, BPC live planning, and Seamless Planning with SAP Datasphere. Use this for planning design, planning APIs, data action debugging, planning performance reviews, and authenticated SAC planning story triage in Microsoft Edge via CDP; use sap-sac-scripting for non-planning SAC scripts and s

Installations / 1h
2
GitHub Stars
497
Mis à jour
13 nov.
secondsky
Communauté

claude-automation-recommender

Analyze a codebase and recommend Claude Code automations (hooks, subagents, skills, plugins, MCP servers). Use when user asks for automation recommendations, wants to optimize their Claude Code setup, mentions improving Claude Code workflows, asks how to first set up Claude Code for a project, or wants to know what Claude Code features they should use.

Installations / 1h
1
GitHub Stars
497
Mis à jour
13 nov.