handoff-updater

Maintains a concise CURRENT-STATE.md handoff document synchronized with each commit.

1|Updated Jun 2, 2026
One-click install
npx skills add https://github.com/psiagoleal/ai-coding-agent-profiles --skill handoff-updater-psiagoleal
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: handoff-updater
Source: https://github.com/psiagoleal/ai-coding-agent-profiles/tree/main/skills/handoff-updater
Command: npx skills add https://github.com/psiagoleal/ai-coding-agent-profiles --skill handoff-updater-psiagoleal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Work progress often depends on verbal reports or re-reading long commit histories, making it hard for the next developer or agent to resume a task. This Skill keeps a living handoff document (docs/CURRENT-STATE.md) updated at every commit so any new session can resume work without reconstructing context. ## Core Features & Use Cases - Commit-linked handoff updates: Records commit hash, completed micro-ticket goals, open blockers, and the suggested next step after each commit or micro-ticket. - Two-file separation: Keeps CURRENT-STATE.md under ~150 lines by moving closed rounds into an append-only docs/handoff-arquivo.md history file, with bidirectional links. - Ready-to-use template: Ships a templates/CURRENT-STATE.template.md with sections for last turn, goals, work in progress, next step, and open blockers. - Use Case: Before ending a coding session, ask the agent to update the handoff; the next developer or AI session reads one short file instead of the full git log. ## Quick Start Update the handoff document with the latest commit, completed goals, open blockers, and the next step before ending this session.

Frequently Asked Questions about handoff-updater

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

FAQPage Schema
How do I keep a project handoff document updated between sessions?▼

Update docs/CURRENT-STATE.md at every commit with the commit hash, completed micro-ticket goals, open blockers, and the suggested next step. Write for someone who was not in the session, avoiding context-dependent jargon.

What should a developer handoff document contain?▼

A handoff should contain the last turn's date, branch, and commit hash, completed goals referencing micro-tickets, work still in progress, open blockers, and the next suggested step. Record root causes of fixes, not just symptoms.

How do I keep a handoff file from growing too large?▼

Keep CURRENT-STATE.md under roughly 150 lines by moving closed rounds verbatim into an append-only docs/handoff-arquivo.md history file. Archive before writing a new entry once the size ceiling is reached, and keep bidirectional links between the two files.

When should the handoff document be updated?▼

Update it at every commit on the working branch, when completing a micro-ticket, and before ending or pausing a session. This guarantees the next turn can resume without re-reading logs.

Should resolved blockers stay in the handoff file?▼

No. A resolved blocker is removed from the living handoff; its resolution is recorded in the round that fixed it inside the history archive. Only still-open blockers remain in CURRENT-STATE.md.