# Claude Md Updater > Use this skill when the user asks to update CLAUDE.md, save a lesson, or persist something from the current session: phrases like "update claude.md", "what should we remember", "save this lesson", or "add to context". Scans the conversation for hard-won lessons, new file paths, infrastructure changes, and new workflows, then proposes scoped edits to the project's CLAUDE.md for approval before wri… - **Type:** Skill - **Install:** `agentstack add skill-jamditis-claude-skills-journalism-claude-md-updater` - **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior - **Seller:** [jamditis](https://agentstack.voostack.com/s/jamditis) - **Installs:** 0 - **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills) - **Latest version:** 0.1.0 - **License:** MIT - **Upstream author:** [jamditis](https://github.com/jamditis) - **Source:** https://github.com/jamditis/claude-skills-journalism/tree/master/dev-toolkit/skills/claude-md-updater - **Website:** https://skills.amditis.tech/ ## Install ```sh agentstack add skill-jamditis-claude-skills-journalism-claude-md-updater ``` Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent. ## About # CLAUDE.md auto-updater Analyze the current conversation to identify information worth persisting in CLAUDE.md for future sessions, then propose the edits for approval before writing anything. ## What to look for ### 1. Hard-won lessons - Debugging sessions that revealed non-obvious causes - Workarounds for platform or tool limitations - Anti-patterns discovered through failure - "The real problem was..." moments ### 2. New infrastructure - New services deployed - New endpoints or URLs - New file paths or directories - New credentials or tokens (reference only, never the values) ### 3. New workflows - Commands that solve recurring problems - Multi-step processes that work well - Integration patterns between systems ### 4. Updated information - Changed ports, IPs, or URLs - New capabilities added to existing systems - Deprecated or removed features ## Analysis process 1. **Scan the conversation** for keywords: - "fixed", "solved", "the issue was", "turns out" - "deployed", "set up", "configured", "installed" - "new endpoint", "new service", "new path" - "doesn't work", "limitation", "workaround" 2. **Categorize findings.** Only durable facts belong in CLAUDE.md: - Hard-won lessons go to the "Hard-won lessons" section - Infrastructure changes update the relevant section - New workflows go to the appropriate section - Transient, session-specific notes do **not** go in CLAUDE.md (see "What not to persist") 3. **Build the exact diff.** Produce a unified diff against the current CLAUDE.md showing the precise lines and sections to be added or changed. This diff is what the user approves, not a summary of it. 4. **Present the diff for approval** and write nothing until the user approves. ## Output format Show the exact patch first, then a short summary grouped by category: ```` ## Proposed CLAUDE.md updates ```diff --- a/CLAUDE.md +++ b/CLAUDE.md @@ section being changed @@ existing context line +new durable lesson, infra fact, or workflow ``` Summary of the diff above: - Hard-won lessons: [one line, if any] - Infrastructure updates: [one line, if any] - New workflows: [one line, if any] Apply this diff? Nothing is written until you approve. ```` ## What not to persist CLAUDE.md is team-shared (checked into git) and advisory: it loads into every session, so it is for durable, infrequently-changing facts, not a running log. Per the project-memory skill, keep these **out** of CLAUDE.md: - Transient "what we did today" session summaries - Anything that changes frequently - Things Claude learns over time through corrections Route those to **auto memory** (`~/.claude/projects//memory/`, which Claude maintains on its own) or to a gitignored `CLAUDE.local.md` for personal notes. Putting them in CLAUDE.md bloats shared context and loads stale per-session facts into future sessions. ## Rules 1. **Never add sensitive values.** Reference where a credential is stored; never include the actual token. 2. **Keep it concise.** CLAUDE.md should stay scannable; target under 200 lines. 3. **Avoid duplication.** Check whether the information already exists before adding it. 4. **Match the existing style.** Follow the tone and format of the current file. 5. **Durable facts only.** Persist hard-won lessons, infrastructure facts, and workflows. Session-specific notes belong in auto memory or a gitignored `CLAUDE.local.md`, never the committed CLAUDE.md. ## Source & license This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code. - **Author:** [jamditis](https://github.com/jamditis) - **Source:** [jamditis/claude-skills-journalism](https://github.com/jamditis/claude-skills-journalism) - **License:** MIT - **Homepage:** https://skills.amditis.tech/ Install and usage instructions live in the source repository linked above. ## Pricing - **Free** — Free ## Security capabilities Automated source analysis of v0.1.0 — what this tool can access: - **Network access:** no - **Filesystem access:** no - **Shell / process execution:** no - **Environment & secrets:** no - **Dynamic code execution:** no *"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.* ## Versions - **0.1.0** — security scan: passed — Imported from the upstream source. ## Links - Listing page: https://agentstack.voostack.com/l/skill-jamditis-claude-skills-journalism-claude-md-updater - Seller: https://agentstack.voostack.com/s/jamditis - Browse the marketplace: https://agentstack.voostack.com/browse --- Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.