session-handoff · rohitg00 — Claude Code skill: what it does, how to install
session-handoff generates a structured handoff document capturing git state, open tasks, decisions, and a resume prompt for your next session.
MIT ★ 2,966 updated 2026-09-29
/plugin marketplace add rohitg00/pro-workflow
/plugin install pro-workflow@pro-workflowWhat session-handoff does
Context disappears once a terminal session closes. Unlike a personal wrap-up checklist, this skill writes specifically for the next agent session, outlining current branch status, uncommitted diffs, and exact lines needing attention.
The workflow queries local git history using git status, git diff --stat, git log --oneline -5, and git branch --show-current. It organizes findings into completed work, in-progress items, key choices with rationale, and unexpected gotchas encountered along the way. At the bottom, it outputs a ready-to-paste resume command.
The target project must be an initialized git repository, or the status collection commands will fail immediately.
What it helps with
- document incomplete tasks before closing the CLI
- preserve architectural decisions and context between sessions
- pinpoint exact file paths and line numbers left mid-work
- produce a copy-paste prompt to restart the next session
Example prompts for the agent
- Wrap up and prepare a session handoff document
- Save progress with session-handoff, I will continue later
- Generate a session transfer note with a resume command
How to install session-handoff
1Plugin marketplace
/plugin marketplace add rohitg00/pro-workflow/plugin install pro-workflow@pro-workflowThis installs the whole pro-workflow plugin with all its skills
2Skills CLI (Vercel)
npx skills add rohitg00/pro-workflow --skill session-handoff -a claude-code3Manually: put the files in place
~/.claude/skills/session-handoff/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/session-handoff/
1Skills CLI (Vercel)
npx skills add rohitg00/pro-workflow --skill session-handoff -a codex2Manually: put the files in place
.agents/skills/session-handoff/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add rohitg00/pro-workflow --skill session-handoff -a cursor2Manually: put the files in place
.cursor/skills/session-handoff/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install rohitg00/pro-workflow skills/session-handoff2Manually: put the files in place
.github/skills/session-handoff/SKILL.md1Skills CLI (Vercel)
npx skills add rohitg00/pro-workflow --skill session-handoff -a gemini-cli2Platform CLI
gemini skills install https://github.com/rohitg00/pro-workflow --path skills/session-handoffManually: put the files in place
.devin/skills/session-handoff/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about session-handoff
How to install session-handoff in Claude Code?
Run both marketplace commands in sequence: first /plugin marketplace add rohitg00/pro-workflow, then /plugin install pro-workflow@pro-workflow.
What makes session-handoff different from wrap-up?
Wrap-up focuses on a personal checklist for the author, while handoff is written strictly as structured input for the next session.
What git commands does session-handoff execute?
It inspects the repository using git status, git diff --stat, git log --oneline -5, and git branch --show-current.
Source text
SKILL.md · MIT
--- name: session-handoff description: Generate a structured handoff document capturing current progress, open tasks, key decisions, and context needed to resume work. Use when ending a session, saying "continue later", "save progress", "session summary", or "pick up where I left off". user-invocable: true --- # Session Handoff Different from wrap-up. Wrap-up is a checklist for *you*. Handoff is a document written for the *next session*. ## Trigger Use when saying "handoff", "continue later", "pass to next session", "session transfer", or ending a session and wanting to resume smoothly. ## Workflow 1. Gather current state from git. 2. List completed, in-progress, and pending work. 3. Note key decisions made and their reasoning. 4. Capture any learnings from this session. 5. Generate a resume command for the next session. ## Commands ```bash git status git diff --stat git log --oneline -5 git branch --show-current ``` ## Output ```markdown # Session Handoff — [date] [time] ## Status - **Branch**: feature/xyz - **Commits this session**: 3 - **Uncommitted changes**: 2 files modified - **Tests**: passing / failing / not run ## What's Done - [completed task 1] - [completed task 2] ## What's In Progress - [current task with context on where you stopped] - [file:line that needs attention next] ## What's Pending - [next task that hasn't been started] - [blocked items with reason] ## Key Decisions Made - [decision 1 and why] - [decision 2 and why] ## Learnings Captured - [Category] Rule (from this session) ## Files Touched - `path/to/file1.ts` — [what changed] - `path/to/file2.ts` — [what changed] ## Gotchas for Next Session - [thing that tripped you up] - [non-obvious behavior discovered] ## Resume Command > Continue working on [branch]. [1-2 sentence context]. Next step: [specific action]. ``` ## Guardrails - Write for the reader (next session), not the writer. - Include specific file paths and line numbers where relevant. - The resume command should be copy-pasteable into the next session. - Keep it factual — describe changes functionally, don't infer motivation.
© Rohit Ghumare · MIT · rohitg00/pro-workflow
Similar skills
All skills for Agent setup: memory, context, orchestration →session-handoff by other authors comes first.