session-handoff
/session-handoff
Creates structured context summaries for continuing work across AI sessions. Use when ending a session to enable seamless continuation in a new session without losing context.
- Author
- ArabelaTso ↗
- Repository
- Skills-4-SE ↗
- Licence
- Apache-2.0
- Last repository change
- 21.08.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 1
No signals detected. Repository changed on 21.08.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
Creates structured context summaries for continuing work across AI sessions. Use when ending a session to enable seamless continuation in a new session without losing context.
Original author description
Creates structured context summaries for continuing work across AI sessions. Use when ending a session to enable seamless continuation in a new session without losing context.
How it works
- When to Use This Skill
- What This Skill Does
- Tips
- Example
SKILL.md preview
--- name: session-handoff description: Creates structured context summaries for continuing work across AI sessions. Use when ending a session to enable seamless continuation in a new session without losing context. --- # Session Handoff Generates a detailed handoff document capturing the current state of work, enabling seamless continuation in a fresh AI session. ## When to Use This Skill - Ending a long coding session that will continue later - Switching between AI tools or models mid-task - Context window approaching limits, need a fresh session - Handing off work to a teammate (human or AI) ## What This Skill Does Generate a structured handoff document with: ### 1. Current State Summary ```markdown ## Session Summary **Task**: [What was being worked on] **Branch**: [Current git branch] **Status**: [In progress / Blocked / Ready for review] **Started**: [When work began] ``` ### 2. What Was Done ```markdown ## Completed Work 1. [Task 1] — [files changed, what was done] 2. [Task 2] — [files changed, what was done] ### Key Decisions Made - Chose X over Y because [reason] - Used pattern Z from [existing file] for consistency ``` ### 3. What Remains ```markdown ## Remaining Work 1. [ ] [Next task] — [specific files, what to do] 2. [ ] [Following task] — [dependencies, approach] ### Blockers - [Any blocking issues with context] ``` ### 4. Relevant Context ```markdown ## Key Files - `src/auth/oauth.ts` — Main implementation file (modified) - `src/auth/types.ts` — Type definitions (new) - `tests/auth/oauth.test.ts` — Tests (partially written) ## Patterns to Follow - Auth middleware pattern from `src/middleware/jwt.ts` - Error handling style from `src/errors/` ## Gotchas Discovered - The `UserService` caches aggressively — clear cache after auth changes - Test DB needs `--runInBand` flag to avoid connection pool exhaustion ## Commands - Build: `npm run build` - Test: `npm test -- --runInBand` - Verify: `npm run typecheck` ``` ### 5. Continuation Instructions ```markdown ## How to Continue 1. Read this handoff document 2. Check `git status` and `git log -5 --oneline` for current state 3. Start with [specific next task] 4. Reference [specific file] for the pattern to follow ``` ## Tips - Write the handoff BEFORE you lose context, not after - Include specific file paths, not vague descriptions - Document gotchas — things that surprised you during the session - Include the exact commands needed to verify work - Keep it under 200 lines — the next session needs room in its context window ## Example **User**: "Create a handoff for this session" **Output**: Generates a structured markdown document covering: 3 completed tasks with file paths, 2 remaining tasks with specific instructions, 4 key files with their roles, 2 gotchas discovered during the session, and exact build/test commands. **Inspired by:** [oh-my-opencode](https://github.com/code-yeongyu/oh-my-opencode) /handoff command
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · ArabelaTso/Skills-4-SE | 100 | Apache-2.0 |
| iuliandita/skills | 100 | MIT |
| cardene777/agent-shuriken | 100 | MIT |
| mcorbett51090/ravenclaude | 100 | MIT |
| upex-galaxy/agentic-qa-boilerplate | 100 | MIT |
| adobe/spectrum-web-components | 100 | Apache-2.0 |
| FrancoStino/opencode-skills-collection | 100 | MIT |
| h2xd/skills | 100 | MIT |
| davila7/claude-code-templates | 100 | MIT |
Database snapshot: 13.11.2026 · package version 34f5615a73e9 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100handoff
Create a structured session handoff document for continuity across sessions. Use when ending a work session, switching contexts, or before a break. Captures decisions, progress, code changes, and next steps so a future session can pick up where you left off without losing context. - 100handoff
Condense the current session into a structured handoff document so the next session or another AI continues without losing context. Use when the context is getting long, before /compact, when ending or splitting a session, when the user says "handoff" or "hand this off", or when… - 100handoff-context
Detects natural language handoff requests and generates structured context summaries for seamless thread continuation. Use when user says "handoff", "new thread", "continue in fresh thread", or similar phrases. - 100handoff
Capture session context for a fresh agent. Use for handoffs, context limits, switching focus, ending sessions, or splitting work across sessions. - 90hermes-session-handoff
Use when a Hermes session, profile, machine, or agent must hand ongoing work to a fresh continuation context without losing verified state, decisions, artifacts, blockers, or the exact next action. - 100handoff
Compact the current conversation into a handoff document so another agent or future session can continue the work without losing context. Use when ending a session, switching tasks, the context is getting long, or user says handoff, wrap up, save progress, or "continue this later".