Agent skill
review-claudemd
CLAUDE.md 리뷰, CLAUDE.md 개선, 대화 분석, 설정 개선, 프롬프트 최적화, 컨텍스트 최적화 - Analyzes recent conversation history to find improvements for global and local CLAUDE.md files. Use when reviewing CLAUDE.md settings, improving Claude Code context, or analyzing past conversations for patterns. Do NOT use for document writing (use doc-coauthoring) or project planning.
Install this agent skill to your Project
npx add-skill https://github.com/aimskr/aims-claude-toolkit/tree/main/skills/review-claudemd
Metadata
Additional technical details for this skill
- author
- jaehashin
- version
- 1.2.0
SKILL.md
Review CLAUDE.md from conversation history
Analyze recent conversations to improve both global (~/.claude/CLAUDE.md) and local (project) CLAUDE.md files.
Step 1: Find conversation history
The project's conversation history is in ~/.claude/projects/. The folder name is the project path with slashes replaced by dashes. bash
Find the project folder (replace / with -)
PROJECT_PATH=$(pwd | sed 's|/|-|g' | sed 's|^-||') CONVO_DIR=~/.claude/projects/-${PROJECT_PATH} ls -lt "$CONVO_DIR"/*.jsonl | head -20
Step 2: Extract recent conversations
Extract the 15-20 most recent conversations (excluding the current one) to a temp directory: bash SCRATCH=/tmp/claudemd-review-$(date +%s) mkdir -p "$SCRATCH" for f in $(ls -t "$CONVO_DIR"/*.jsonl | head -20); do basename=$(basename "$f" .jsonl)
Skip current conversation if known
cat "$f" | jq -r ' if .type == "user" then "USER: " + (.message.content // "") elif .type == "assistant" then "ASSISTANT: " + ((.message.content // []) | map(select(.type == "text") | .text) | join("\n")) else empty end ' 2>/dev/null | grep -v "^ASSISTANT: $" > "$SCRATCH/${basename}.txt" done ls -lhS "$SCRATCH"
Step 3: Spin up Sonnet subagents
Launch parallel Sonnet subagents to analyze conversations. Each agent should read:
- Global CLAUDE.md: ~/.claude/CLAUDE.md
- Local CLAUDE.md: ./CLAUDE.md (if exists)
- Batch of conversation files Give each agent this prompt template:
Read:
- Global CLAUDE.md: ~/.claude/CLAUDE.md
- Local CLAUDE.md: [project]/CLAUDE.md
- Conversations: [list of files] Analyze the conversations against BOTH CLAUDE.md files. Find:
- Instructions that exist but were violated (need reinforcement or rewording)
- Patterns that should be added to LOCAL CLAUDE.md (project-specific)
- Patterns that should be added to GLOBAL CLAUDE.md (applies everywhere)
- Anything in either file that seems outdated or unnecessary Be specific. Output bullet points only.
Batch conversations by size:
- Large (>100KB): 1-2 per agent
- Medium (10-100KB): 3-5 per agent
- Small (<10KB): 5-10 per agent
Step 4: Aggregate findings
Combine results from all agents into a summary with these sections:
- Instructions violated - existing rules that weren't followed (need stronger wording)
- Suggested additions - LOCAL - project-specific patterns
- Suggested additions - GLOBAL - patterns that apply everywhere
- Potentially outdated - items that may no longer be relevant Present as tables or bullet points. Ask user if they want edits drafted.
Completion
분석 결과(violations, suggested additions, potentially outdated)가 집계되고 사용자가 검토하면 완료.
Troubleshooting
Conversation history is empty or too few files: Check the project path mapping (slashes → dashes). If the user started with a different project path, the folder name won't match. Subagents return conflicting recommendations: Prioritize by frequency — if 3+ agents flag the same pattern, it's a strong signal. Unique findings need manual user review. CLAUDE.md is already well-optimized: Focus on Step 4 "potentially outdated" items. Even good configs accumulate stale rules over time.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
build-error-resolver
빌드 에러, 빌드 오류, 컴파일 에러, 빌드 실패 해결, 의존성 에러 - Specialized in resolving build errors, compilation failures, and dependency issues. Use when build fails, compilation errors occur, or dependency conflicts arise. Do NOT use for runtime bugs or logic errors (use debug-specialist instead).
brainstorming
브레인스토밍, 아이디어, 기획, 구상, 아이디어회의, 설계, 요구사항 분석, 접근법 탐색 - Use before creating new features or significant changes to explore user intent, requirements, and design options. Collaborative brainstorming through step-by-step questioning. Do NOT use for simple bug fixes, config changes, or tasks with clear requirements already defined.
doc-coauthoring
문서 작성, 문서화, 문서, 스펙 작성, 기술 문서, 제안서, RFC, 설계 문서, 의사결정 문서 - Collaborative document co-authoring through 3 stages: context gathering, iterative refinement, and reader testing. Use when writing docs, proposals, tech specs, decision docs, or RFCs. Do NOT use for PRD/product requirements (use prd-strategist) or implementation plans (use writing-plans).
testing-strategy
테스트 전략, 테스팅 계획, QA 전략, 품질 보증, 테스트 피라미드, 테스트 시나리오, 커버리지 목표 - Designs test strategies including test pyramid ratios, scenario categories, and coverage targets. Use when planning how to test a feature, designing QA approach, or creating test plans. Do NOT use for TDD implementation (use tdd-workflow) or E2E test execution (use e2e-runner).
learning-research
학습 리서치, 학습 자료, 공부 자료, 학습, 공부, 스터디, 개념 정리, 이해 - 특정 주제를 깊이 이해하기 위한 학습 자료를 수집·정리한다. 병렬 전문가 서브에이전트로 개념, 원리, 실습, 심화 자료를 수집하고 이해도별로 체계화된 학습 노트를 생성한다. Obsidian vault에 자동 저장. 의사결정용 자료 조사는 research 스킬을, 시장조사는 market-research 스킬을 사용할 것.
devil-advocate
Didn't find tool you were looking for?