Session handoff

Skill henriquescastilho/my-claude/.codex/vendor_imports/claude/marketplaces/pro-workflow/skills/session-handoff

Setup público e sanitizado de um Claude Code full-stack: 8 sub-agents com roteamento por modelo, 792 skills, hooks de segurança, MCP servers e metodologia opinativa. Desenhado para um agente de IA se auto-configurar.

Install

npx -y skills add henriquescastilho/my-claude --skill session-handoff

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

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

SKILL.md

2.1 KB, 457 tokens by cl100k_base, as published. Nobody here has run it

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

Gather current state from git.
List completed, in-progress, and pending work.
Note key decisions made and their reasoning.
Capture any learnings from this session.
Generate a resume command for the next session.

Commands

git status
git diff --stat
git log --oneline -5
git branch --show-current

Output

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