claude-md-updater

# 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 ...