Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From claude-md-management
Reflects on the current session, identifies missing context, and updates CLAUDE.md with concise learnings to improve future sessions. Shows proposed changes as diffs and applies with approval.
How this command is triggered — by the user, by Claude, or both
Slash command
/claude-md-management:revise-claude-mdThis command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
Review this session for learnings about working with Claude Code in this codebase. Update CLAUDE.md with context that would help future Claude sessions be more effective. ## Step 1: Reflect What context was missing that would have helped Claude work more effectively? - Bash commands that were used or discovered - Code style patterns followed - Testing approaches that worked - Environment/configuration quirks - Warnings or gotchas encountered ## Step 2: Find CLAUDE.md Files Decide where each addition belongs: - `CLAUDE.md` - Team-shared (checked into git) - `.claude.local.md` - Persona...
Review this session for learnings about working with Claude Code in this codebase. Update CLAUDE.md with context that would help future Claude sessions be more effective.
What context was missing that would have helped Claude work more effectively?
find . -name "CLAUDE.md" -o -name ".claude.local.md" 2>/dev/null | head -20
Decide where each addition belongs:
CLAUDE.md - Team-shared (checked into git).claude.local.md - Personal/local only (gitignored)Keep it concise - one line per concept. CLAUDE.md is part of the prompt, so brevity matters.
Format: <command or pattern> - <brief description>
Avoid:
For each addition:
### Update: ./CLAUDE.md
**Why:** [one-line reason]
\`\`\`diff
+ [the addition - keep it brief]
\`\`\`
Ask if the user wants to apply the changes. Only edit files they approve.
npx claudepluginhub p/lucianocalixtogil-gif-claude-md-management-plugins-claude-md-management31plugins reuse this command
First indexed Jan 22, 2026
Showing the 6 earliest of 31 plugins
/revise-claude-mdReflects on the current session, identifies missing context, and updates CLAUDE.md with concise learnings to improve future sessions. Shows proposed changes as diffs and applies with approval.
/save-session-learningsDocuments session learnings into CLAUDE.md and AGENTS.md by analyzing git history and conversation context, categorizing findings, and updating project documentation.
/learnMines the current conversation for recurring corrections and durable lessons, then proposes additions to CLAUDE.md to prevent repeating mistakes.
/memory-bankUpdates the project's CLAUDE.md memory bank with learnings from the current session, including decisions, problems solved, patterns, commands, and dependencies.
/session-learning-captureCaptures learnings from the current session and writes them to CLAUDE.md or CLAUDE.local.md files for future reference.
/update-claudemdAnalyzes recent git history and project structure to automatically update a project's CLAUDE.md file, preserving existing context and integrating new features, API changes, and configuration updates.