Skip to content
Back to skills

Session Handoff

ASecurity

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".

  • 2,892 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added May 28, 2026
ai-agentsgobashrailsgit

Security analysis

A100/100

Scanned May 28, 2026

npx -y skills add rohitg00/pro-workflow --skill session-handoff --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Session Handoff?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Session Handoff
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/rohitg00-session-handoff/badge)](https://www.skillsdirectory.com/skills/rohitg00-session-handoff)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
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".
---

# 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.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.