dev-docs-update

Updates active task documentation and commits git state before context compaction.

16|1|Updated May 5, 2026
One-click install
npx skills add https://github.com/AIBiz-Automatyzacje/workspace-template-mobile --skill dev-docs-update-aibiz-automatyzacje
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dev-docs-update
Source: https://github.com/AIBiz-Automatyzacje/workspace-template-mobile/tree/main/.claude/skills/dev-docs-update
Command: npx skills add https://github.com/AIBiz-Automatyzacje/workspace-template-mobile --skill dev-docs-update-aibiz-automatyzacje

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a Claude Code session approaches the context limit, in-progress work details risk being lost. This Skill preserves session state by updating task documentation and securing git state so work can resume seamlessly after a context reset. ## Core Features & Use Cases - Git State Protection: Saves the current branch, commits uncommitted changes as WIP, and records the latest commit hash before any documentation update. - Structured Doc Updates: Updates plan, context, and task checklist files in docs/active/ following a strict parser contract (checkbox formats, phase tables, decision logs). - Handoff Notes: Writes a handoff section with branch, commit, exact file/line being edited, and verification commands for post-restart continuation. - Use Case: Mid-implementation of a mobile feature, the context window fills up. Run this Skill to commit WIP changes, mark completed checkboxes, log decisions, and generate restart instructions for the autopilot workflow. ## Quick Start Ask the assistant to update the dev documentation for the current task folder before the context resets.

Frequently Asked Questions about dev-docs-update

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I preserve work progress before a Claude Code context reset?▼

Run this Skill to commit uncommitted changes as a WIP commit, update the task's plan, context, and checklist files in docs/active, and write a handoff section with branch, commit hash, and restart commands.

How do I update task checklists in docs/active folders?▼

Change completed implementation checkboxes from - [ ] to - [x] without adding extra text. Never manually check Verification or [E2E] items, since only the review workflow marks those after real test runs.

Can I manually edit autopilot state files or phase statuses?▼

No. The .autopilot-state.json file is the source of truth for phases, and checkboxes are only a view. Changing state requires a fresh autopilot run rather than manual edits.

What happens if uncommitted changes exist after the documentation update?▼

The autopilot bootstrap stops the run when it detects uncommitted changes. The Skill requires git status to be completely clean after the final documentation commit.

When should I use this Skill instead of a normal commit?▼

Use it specifically when approaching the context limit during an active task. It combines WIP commits with structured documentation updates and handoff notes, which a plain commit does not capture.