skills.rest
surfingalien
surfingalienCOMMUNITY
Explore all skills by this author →
GitHub

session-handoff

Generates a structured handoff document capturing session progress, decisions, and resume context.

1|Updated May 6, 2026
Search Tags:#git#workflow#documentation#markdown#progress tracking#session handoff#context transfer
One-click install
npx skills add https://github.com/surfingalien/FinSurfing --skill session-handoff-surfingalien
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: session-handoff
Source: https://github.com/surfingalien/FinSurfing/tree/main/.claude/skills/session-handoff
Command: npx skills add https://github.com/surfingalien/FinSurfing --skill session-handoff-surfingalien

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Ending a work session without a clear record of progress, decisions, and next steps makes resuming work slow and error-prone. This Skill produces a structured handoff document so the next session can pick up exactly where you left off. ## Core Features & Use Cases - Git-Based State Capture: Runs git status, diff, log, and branch commands to ground the handoff in the actual repository state. - Structured Handoff Template: Produces a Markdown document covering completed work, in-progress tasks, pending items, key decisions, learnings, files touched, and gotchas. - Resume Command: Generates a copy-pasteable resume instruction for the next session. - Use Case: Before ending a coding session on a feature branch, ask for a handoff to document uncommitted changes, the exact file and line where work stopped, and the next concrete action. ## Quick Start Ask the assistant to create a session handoff summarizing current progress and next steps before ending this session.

Frequently Asked Questions about session-handoff

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

FAQPage Schema
How do I create a session handoff document before ending work?▼

Ask for a session handoff and the Skill gathers git state, lists completed and pending work, records key decisions, and outputs a structured Markdown document with a resume command for the next session.

What is the difference between a session handoff and a wrap-up checklist?▼

A wrap-up is a checklist for yourself, while a handoff is a document written for the next session or person. The handoff focuses on context, decisions, and a concrete resume command rather than task verification.

What information does a session handoff document include?▼

It includes branch and commit status, completed and in-progress tasks, pending items, key decisions with reasoning, learnings, files touched, gotchas, and a copy-pasteable resume command.

Does the session handoff require a git repository?▼

Yes, the workflow runs git status, git diff --stat, git log, and git branch --show-current to capture repository state, so it expects to run inside a git repository.

When should I use a session handoff instead of a commit message?▼

Use it when work is incomplete or spans uncommitted changes, since commit messages only cover committed code. The handoff captures in-progress context, blockers, and next steps that commits cannot express.

Related Skills

Explore More Software Engineering Skills→
berserkdisruptorsberserkdisruptors
145

recall

Reconstruct development context from git commit history into structured intent and decision lines.

Official
Advanced
ResgridResgrid
224

session-management

Load and persist .NET project context across AI engineering sessions.

Official
Advanced
joshka0joshka0
3

Remember

Save key learnings, decisions, and gotchas into foxctl memory with typed classification.

Community
Basic
ma08ma08
28

save-status

Persist task status files and reconcile session metadata across machines.

Community
Advanced