session-end
Skill288 starsChanged 12 days agoMITView on GitHub
Use when the user asks to end, wrap up, clear, hand off, or prepare continuity for a Codex/AgentDeck session. Closes out in-flight work (uncommitted changes, worktrees, open PRs), records only what the next reader cannot get from git, and writes a concise handoff for the next session.
28 other projects use a version of this.
Adopted by
Most recently taken up by
- spizganed/skillstheir own version, first seen Nov 8, 2026
- edxleon/runspectortheir own version, first seen Nov 8, 2026
- salvo8519/fairmarktheir own version, first seen Nov 8, 2026
- ravindu57/SCMLtheir own version, first seen Nov 1, 2026
- IlyaGorsky/memory-toolkittheir own version, first seen Nov 1, 2026
- cedaniel200/atlas-templatetheir own version, first seen Nov 1, 2026
Used with
Projects with it also use session-start and ship.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
bitwize-music-studioSkillsession-start
Runs the session startup procedure - verifies setup, loads config and state, checks skill models, and reports project status. Use at the beginning of a fresh session.
Also in 11 projects that use this
AWSSkillship
Finalize dev work on an issue branch — update docs, push, and open a PR.
Also in 3 projects that use this
Other versions28 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 28
- faizkhairi/claude-code-blueprint★ 73same name
- Kanevry/session-orchestrator★ 53same name
- valpere/session-indexer★ 42same name
- namedtoaster/The-Last-Mile★ 39same name
- iamneilroberts/claude-skills★ 26same name
- IlyaGorsky/memory-toolkit★ 13same name
- edxleon/runspector★ 9same name
- mae616/ai-template★ 9same name
- freskhu/genesis★ 5same name
- jkm-4314/claude-code-skills★ 4same name
18 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository6 other files it gives its agents.
- AGENTS.mdAGENTS.md
- esp32/AGENTS.mdAGENTS.md
- agentdeck-deploySkill
- agentdeck-workflowsSkill
- esp32-heap-disciplineSkill
- sdc-diagnoseSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 3 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 21 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 18
Do not read DEVELOPMENT_LOG.md or the devlog entries here.
- Distinctive: line 22
Uncommitted changes: Commit them on the task branch, or name them in the handoff as deliberately left uncommitted.
- Distinctive: line 23
Worktrees this session created: Remove one only when its branch is pushed, its tree is clean, and no other session owns it (AGENTS.md § …
- Very specific: line 36
Update AGENTS.md only for a project-wide workflow or invariant change, and stay inside its byte budget (pnpm docs:check).
- Distinctive: line 51
Keep it short enough to paste into a new prompt.
“Common” is measured: kept by at least 6 in 10 of the 21 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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. Its job is a handoff the next session can act on without the transcript. It does not create a record of everything that happened; git, the PRs and the issues already hold that.
1. Read the state (cheap commands only)
git status -sb
git worktree list
gh pr list --author @me --state open --json number,title,headRefName,mergeableDo not read DEVELOPMENT_LOG.md or the devlog entries here. Nothing in the handoff depends on them.
2. Close out what this session started
- Uncommitted changes. Commit them on the task branch, or name them in the handoff as deliberately left uncommitted. Never revert, stash, or restore another session's changes in a shared tree.
- Worktrees this session created. Remove one only when its branch is pushed, its tree is clean, and no other session owns it (
AGENTS.md§ Agent working agreements). Otherwise list it with the reason it stays. - PRs this session opened. List each with its state: CI, mergeable, review, and what blocks it.
- Background agents or long commands. Say whether each is still running. Never report a result you have not received.
3. Record only what git cannot
| What you learned | Where it goes |
| A domain invariant (a rule future edits must keep) | the matching .claude/rules/<domain>.md. Move the rule body there verbatim; never paraphrase it |
| A measurement, incident, pitfall, or decision with its rejected alternatives | one new file docs/devlog/entries/YYYY-MM-DD-<slug>.md (line 1 # YYYY-MM-DD — title, ### sections, links relative to the repo root), committed with the change. Nothing to regenerate |
| A personal preference or dated retrieval hint | agent memory (local, not the repo) |
| What changed and why | nothing: the diff and the PR body already say it |
Update AGENTS.md only for a project-wide workflow or invariant change, and stay inside its byte budget (pnpm docs:check). Never write secrets, tokens, device passcodes, or raw transcripts into any of these.
4. Handoff
**Session Handoff**
- Goal:
- Current state: (merged / open PRs with blockers / uncommitted work)
- Worktrees and branches left:
- Verification: (what ran, result)
- Open issues / risks:
- Next action: (one concrete step)
- Records written: (devlog entry / rule / memory, or "none — git holds it")Keep it short enough to paste into a new prompt. Give file paths and PR numbers, not diffs.
Notes
- Codex: use
/compactto keep going with compressed context, and/newto start fresh after the handoff. - Claude Code: use
/clearto start fresh after the handoff. - Link to a canonical rule rather than copying it. An old approval or release condition is a dated fact, not a permanent gate.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.