skills.rest
RisorseArtificiali
RisorseArtificialiOFFICIAL
Explore all skills by this author →
WebsiteGitHub

handoff

Writes a handoff document summarizing the current conversation for a fresh agent session.

9|1|Updated Aug 28, 2026
Search Tags:#git#documentation#agent workflow#handoff#session continuity#context compaction
One-click install
npx skills add https://github.com/RisorseArtificiali/skills --skill handoff-risorseartificiali
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: handoff
Source: https://github.com/RisorseArtificiali/skills/tree/main/forked/handoff
Command: npx skills add https://github.com/RisorseArtificiali/skills --skill handoff-risorseartificiali

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a coding session ends or context runs out, the next agent session starts cold with no memory of prior decisions, progress, or open questions. This Skill compacts the current conversation into a structured handoff document so a fresh agent can resume the work without losing context. ## Core Features & Use Cases - Conversation Compaction: Summarizes the current session into a Markdown handoff document saved to .reviews/handoffs/<date>-<topic>.md inside the repository, with a fallback to the OS temp directory outside git repos. - Lifecycle Management: Keeps only pending handoffs in handoffs/ by embedding an instruction in every document telling the resuming agent to move it to handoffs/done/ after reading. - Context Discipline: References existing artifacts (specs, plans, ADRs, commits) by path instead of duplicating them, redacts sensitive data like API keys, and suggests skills the next agent should invoke. - Use Case: Before ending a long debugging session, invoke the handoff skill with a note like "next session: finish the Maven test fixes" so tomorrow's agent picks up exactly where you left off. ## Quick Start Ask the agent to create a handoff document for the next session, optionally describing what that session will focus on.

Frequently Asked Questions about handoff

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

FAQPage Schema
How do I pass work between agent sessions without losing context?▼

Invoke the handoff skill at the end of a session. It writes a summary document to .reviews/handoffs/ in the repository, and the next session's agent reads it to resume the work with full context.

Where are handoff documents stored?▼

Inside a git repository they are saved to .reviews/handoffs/<date>-<topic>.md, with .reviews/ excluded via .git/info/exclude rather than .gitignore. Outside a repository, the OS temporary directory is used as a fallback.

What happens to a handoff document after it is read?▼

Every handoff starts with an instruction telling the resuming agent to move the file to .reviews/handoffs/done/ after reading. This keeps the handoffs directory listing only pending work while preserving consumed documents.

Does the handoff document duplicate specs, plans, or commits?▼

No. The skill references existing artifacts such as specs, plans, ADRs, issues, commits, and diffs by path or URL instead of copying their content, keeping the handoff compact and free of stale duplicates.

Is sensitive information included in handoff documents?▼

No. The skill explicitly redacts sensitive information such as API keys, passwords, and personally identifiable information before writing the handoff document.

Related Skills

Explore More Software Engineering Skills→
tranhieutttranhieutt
70

save-state

Write current task, progress, decisions, and blockers to production/session-state/active.md.

Community
Intermediate
garyjgaryj

pickup

Load a handoff file from .claude/handoffs to resume work.

Community
Basic
hbvg234hbvg234
1

handoff

Summarize the current conversation into a structured handoff document referencing artifacts by path or URL.

Community
Intermediate
ComputerConnectionComputerConnection

resume

Aggregate handoffs, git history, and project state into a structured resume brief.

Community
Intermediate