session-stop
Skill1 starsChanged 3 months agoMITView on GitHub
Close a work session — save the repo memory, pass the hard gate, and commit & push everything so nothing is forgotten and nothing is left half-done. Counterpart to session-start. Trigger: "session-stop", "session-end", "wrap up", "end session", "done for today", "close the session", "sauber abschließen", end of a work session.
In this repository5 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- contextSkill
- project-stateSkill
- session-startSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
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 14
If claude-mem is available, query it for this session's decision and discovery observations and use them as *candidates* — then decide per …
- Distinctive: line 16
Write the judgment, never copy an observation verbatim.
- Very specific: line 19
Write the HANDOFF entry: run ./scripts/session-snapshot.sh <today's-date> and fill in Done / Decided / Open / Next / Continuity warnings at …
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
session-stop
Nothing forgotten, nothing half-done. Deterministic checks gate the close.
Steps
- Rescue the chat (mandatory). Any idea, decision, or owner instruction that lives only in
this conversation is lost unless written down now. Capture it into
HANDOFF.md/BIBLE.md. If claude-mem is available, query it for this session'sdecisionanddiscoveryobservations and use them as candidates — then decide per item: BIBLE entry, HANDOFF entry, or nothing. Write the judgment, never copy an observation verbatim. Without claude-mem, work from the conversation directly. - Record durable decisions in
BIBLE.md's decision register (date · decision · why). - Write the HANDOFF entry: run
./scripts/session-snapshot.sh <today's-date>and fill in Done / Decided / Open / Next / Continuity warnings at the top ofHANDOFF.md(newest first). - Pass the gate:
./scripts/gate.shmust printGATE: PASS. Fix reds; never commit over a red gate. - Update
CHANGELOG.mdunder[Unreleased]if user-facing behaviour changed. - Commit granularly — Conventional Commits, one concern per commit. No sweep commit.
- Push, then run
./scripts/secure.sh— it must printSECURE: all saved.
Report the final gate + secure status in one line.
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.

