---
name: Session End
slug: session-end
category: Automation
description: Session End helps wrap up a Codex or AgentDeck session by summarizing work, checking changed files, and preparing a concise handoff. Use it before `/clear`, `/new`, or switching tasks so the next session can continue quickly.
github: "https://github.com/puritysb/AgentDeck/tree/master/.agents/skills/session-end"
language: TypeScript
stars: 219
forks: 42
install: "npx degit https://github.com/puritysb/AgentDeck/tree/master/.agents/skills/session-end ~/.claude/skills/session-end"
installs_to: ~/.claude/skills/session-end
source_path: .agents/skills/session-end/SKILL.md
collection_size: 5
category_size: 1860
collection_url: "https://dirskills.com/collections/puritysb/AgentDeck"
added: 2026-09-04T05:25:08.520Z
last_synced: 2026-09-04T05:25:08.520Z
canonical_url: "https://dirskills.com/skills/session-end"
---

# Session End

Session End helps wrap up a Codex or AgentDeck session by summarizing work, checking changed files, and preparing a concise handoff. Use it before `/clear`, `/new`, or switching tasks so the next session can continue quickly.

**Install:**

```bash
npx degit https://github.com/puritysb/AgentDeck/tree/master/.agents/skills/session-end ~/.claude/skills/session-end
```

## README

# 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 updated:
```

Keep it short enough to paste into a new Codex prompt. Include file paths for changed files, but avoid dumping large diffs.

## Notes

- Use Codex `/compact` when the active thread should continue with a compressed context.
- Use `/new` or `/clear` after the handoff when the next task should start fresh.
- Use Codex Memories for personal recurring preferences only; required AgentDeck rules belong in checked-in docs.