Memory Update — Development skill for Claude Code
Updates .claudememory with decisions and tasks completed in the session.
How to install Memory Update
Installs to ~/.claude/commands/drlux-claude-code-template-memory-update.md
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/DrLux/claude-code-template/HEAD/.claude/commands/memory-update.md -o ~/.claude/commands/drlux-claude-code-template-memory-update.md Restart Claude Code, or start a new session, for it to be picked up.
What Memory Update does
name: memory-update description: Updates .claudememory with decisions and tasks completed in the session
Analyze the current session and update `.claudememory`:
- Add to "Recent Technical Decisions" the choices made today (with date).
- Mark resolved TODOs as completed [x].
- Add new TODOs identified during work.
- Update "Features in Development" with the current status.
Do not delete history: add at the top of sections. Keep the file under 100 lines: archive decisions > 30 days
Alternatives in Development
- Projectmem — Open-source coding agent memory 766 ★
- Arrecall — AgentRecall on-demand recall — surface past fixes, decisions, and patterns mid-session without leaving your fl 370 ★
- Memory Question — Ask Claude's memory system questions about past work, decisions, and context 332 ★
Full documentation available on GitHub
View Source RepositoryRelated Skills
Migrate Followups
Consolidate the migrated repos' open follow-ups (owner decisions, tasks, deferrals) and update them at the sou
Bullpen Config
View or update bullpen configuration. Without arguments, shows the current settings. With "set ", updates one
MCP Tasks Optimize Prompts
Analyze session events from completed stories to optimize prompts
Orgx MCP
Organizational memory and agent orchestration MCP. Remember decisions, artifacts, tasks, and project context a
Al Memory.Create.Prompt
Generate or update memory.md file tracking decisions, changes, and learnings throughout project development fo
Memory Shard Roll
Close finished calendar years out of an over-ceiling log-topic file (worklog/support/decisions) into a locked
Related Agents
Neo Shadow
Memory keeper. MUST BE USED to save session context into the second brain (.neo/brain/) — at task boundaries,
Taskmaster
Maintain docs/todos.md as the canonical Gemma-Code progress tracker. Reads recent commits, open issues, merged
End Session
Use at the end of every working session. Chains learn → memory update → drift check → status update in the cor