---
description: End-of-session handoff — verify work is saved, update AGENTS.md durable knowledge and Current state, propose commit and push
argument-hint: [optional focus notes]
allowed-tools: Bash(git:*), Read, Edit, Write, Grep, Glob
---

# Session handoff

I'm about to end this session. Run the close-out checklist below. Use judgment — skip any step that doesn't apply to what we did this session, and tell me what you skipped and why. Optional focus notes from me (may be empty): $ARGUMENTS

## 1. Verify the work is on disk

- If this is a git repo, run `git status` and report any uncommitted or untracked changes related to this session's work.
- If meaningful work is uncommitted, propose a commit (or a few logical commits) with clear messages. Wait for my approval before committing — do not commit on your own. After committing, push if a remote is configured.
- If this is not a git repo, list every file we created or modified this session and confirm each one is actually written to disk, not just discussed in conversation.

## 2. Update AGENTS.md — durable knowledge only

- Add or refresh only what every future session will need: architectural decisions made, conventions or patterns established, gotchas discovered, key commands, dependency or structure facts we learned the hard way.
- Keep it lean. AGENTS.md loads at the start of every future session, so no session narrative, no play-by-play. If anything in it is now obsolete or contradicted by today's work, fix or remove it.
- If a piece of guidance is subsystem-specific rather than whole-repo, put it in docs/guides/<topic>.md with paths: frontmatter, symlink it from .claude/rules/, and add its one-line index entry in AGENTS.md instead.

## 3. Update the Current state section — session state

- Rewrite the `## Current state` section at the bottom of AGENTS.md. It represents current state, not a running log — overwrite, don't append. Present tense, 15 lines max. Cover:
  - What's done and working, including anything finished this session
  - What's in progress and exactly where it stands
  - Next steps in priority order
  - Open questions, risks, or anything I flagged that we didn't resolve
  - Test/build status if worth knowing
- Anything longer-term goes in ROADMAP.md, not here. If Current state is accumulating history, prune it — history lives in the git log.

## 4. Final report

Reply with a short summary: what got committed or pushed, what went into durable knowledge versus Current state, and anything still unresolved. If everything is clean, say it's safe to exit. Then, in case I decide to keep this session alive instead, give me a one-line `/compact Focus on ...` command tailored to what matters most from this session.