session-end

Solid

Use when the user asks to end, wrap up, clear, hand off, or prepare continuity for a Codex/AgentDeck session. Summarizes current work, captures next-step memory, updates durable project notes only when needed, and writes a concise handoff for the next session.

AI & Automation 167 stars 29 forks Updated yesterday MIT

Install

View on GitHub

Quality Score: 84/100

Stars 20%
74
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
97
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Session End Use this skill at the end of a work session, before `/clear`, `/new`, switching tasks, or handing work to another Codex/Claude session. ## Purpose Produce a concise handoff that lets the next session continue without rereading the whole transcript. Separate temporary handoff notes from durable project knowledge. ## Workflow 1. Read `CLAUDE.md` and the top of `DEVELOPMENT_LOG.md`. 2. Inspect the current work state: ```bash git status --short git diff --stat ``` 3. If files changed, inspect only relevant diffs needed to summarize the work. Do not revert unrelated changes. 4. Summarize: - goal and current outcome - files changed and why - verification run and results - unresolved risks or blockers - exact next action for the next session 5. Update durable docs only when warranted: - `DEVELOPMENT_LOG.md`: add an entry for meaningful fixes, architectural decisions, hardware findings, or known pitfalls. - `CLAUDE.md`: update only for project-wide architecture, invariants, setup, or workflow changes. - `AGENTS.md`: update only for persistent agent behavior expectations. 6. Do not write secrets, credentials, tokens, private device passcodes, or raw prompt transcripts into durable docs. 7. If no durable doc update is warranted, say so explicitly in the final handoff. ## Handoff Format Return this shape: ```markdown **Session Handoff** - Goal: - Current state: - Changed files: - Verification: - Open issues: - Next action: - Durable docs u...

Details

Author
puritysb
Repository
puritysb/AgentDeck
Created
5 months ago
Last Updated
yesterday
Language
C
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

session-handoff

Use when the user says "session handoff", "wrap up session", "hand off", "handoff summary", "let's wrap up", "summarize before I clear", or wants a structured end-of-session summary before clearing context. Also use proactively when the user says they are about to /clear and no handoff has been produced yet. Generates a handoff document saved as a file (in the project's docs/handoffs/ directory, or as a downloadable file in chat environments) with required sections (objective, status, decisions + rationale, key files, next action) plus situational sections included only when they apply, so a fresh agent can continue seamlessly without re-deriving lost context.

2 Updated 1 weeks ago
AdityaVasireddy
AI & Automation Listed

session-handoff

Write a start-here handoff document at the end of a work session capturing state, decisions, next steps, and gotchas, so the next session (or the next person) resumes in minutes instead of re-deriving everything. Use when the user says "wrap up", "handoff", "end of session", "write a handoff note", or "where did we leave off" at the start of a new session.

2 Updated 2 weeks ago
jqaisystems
Web & Frontend Solid

handoff

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.

102 Updated 1 weeks ago
robertguss