dev-docs-update — Claude Code command: install and use
The dev-docs-update command records active work before a context reset, covering task files, project memory, unfinished work, and handoff notes.
MIT ★ 10,055 updated 2026-07-13
.claude/commands/dev-docs-update.mdWhat dev-docs-update does
dev-docs-update refreshes development records when a session is nearing its context limit. It processes each task under /dev/active/, writing the current implementation state, session decisions, changed files, blockers, and next steps. It also revises task lists by marking finished work and adding newly discovered items.
The command captures details that are easy to lose between sessions: solved technical problems, architecture choices, bugs, integrations, test methods, and performance changes. When relevant, it stores new patterns in project memory and records the exact stopping point, restart commands, temporary workarounds, and handoff details.
An optional argument can narrow the update to a particular task or area. Tasks outside /dev/active/ are not covered by that part of the command.
What it helps with
- record active work before a context reset
- refresh context files under
/dev/active/ - mark completed tasks and add newly found work
- preserve blockers, decisions, and restart commands
- prepare notes for a clean session handoff
Example prompts for the agent
- Run
/dev-docs-updateand record the current session state. - Use
/dev-docs-updatewith focus on the authentication task. - Before the context resets, run
/dev-docs-updateand capture unfinished work.
How to install dev-docs-update
Manually: put the files in place
.claude/commands/dev-docs-update.mdCall it with /dev-docs-update. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/dev-docs-update.mdCall it with /prompts:dev-docs-update. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/dev-docs-update.prompt.mdManually: put the files in place
.gemini/commands/dev-docs-update.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about dev-docs-update
How do I install dev-docs-update in Claude Code?
Create the command file at .claude/commands/dev-docs-update.md and place the command content there.
Does dev-docs-update work with Codex?
Yes. For Codex, place the file at ~/.codex/prompts/dev-docs-update.md.
What does dev-docs-update do?
It updates active task documentation, preserves session decisions and unfinished work, and creates handoff notes for continuing after a context reset.
Source text
dev-docs-update.md · MIT
--- description: Update dev documentation before context compaction argument-hint: Optional - specific context or tasks to focus on (leave empty for comprehensive update) --- We're approaching context limits. Please update the development documentation to ensure seamless continuation after context reset. ## Required Updates ### 1. Update Active Task Documentation For each task in `/dev/active/`: - Update `[task-name]-context.md` with: - Current implementation state - Key decisions made this session - Files modified and why - Any blockers or issues discovered - Next immediate steps - Last Updated timestamp - Update `[task-name]-tasks.md` with: - Mark completed tasks as ✅ - Add any new tasks discovered - Update in-progress tasks with current status - Reorder priorities if needed ### 2. Capture Session Context Include any relevant information about: - Complex problems solved - Architectural decisions made - Tricky bugs found and fixed - Integration points discovered - Testing approaches used - Performance optimizations made ### 3. Update Memory (if applicable) - Store any new patterns or solutions in project memory/documentation - Update entity relationships discovered - Add observations about system behavior ### 4. Document Unfinished Work - What was being worked on when context limit approached - Exact state of any partially completed features - Commands that need to be run on restart - Any temporary workarounds that need permanent fixes ### 5. Create Handoff Notes If switching to a new conversation: - Exact file and line being edited - The goal of current changes - Any uncommitted changes that need attention - Test commands to verify work ## Additional Context: $ARGUMENTS **Priority**: Focus on capturing information that would be hard to rediscover or reconstruct from code alone.
© diet103 · MIT · diet103/claude-code-infrastructure-showcase