session-close
Skill0 starsChanged 47 days agoMITView on GitHub
Close a work session in a file-first AI workbench. Captures decisions and learnings, rewrites the desk file, runs scripts/check, commits on a branch and opens a pull request. Use at the end of every session, and whenever git status shows work that would otherwise be lost.
22 other projects use a version of this.
Adopted by
Most recently taken up by
- kimkon1011/orgiast-claude-rulestheir own version, first seen Nov 8, 2026
- paureis/pau-skillstheir own version, first seen Nov 8, 2026
- pankaj-mahaur/Agent-Daemontheir own version, first seen Nov 6, 2026
- NathanForster/claude-commandstheir own version, first seen Nov 1, 2026
- ngmeyer/skillstheir own version, first seen Nov 1, 2026
- albertomarturelo/siitheir own version, first seen Nov 1, 2026
Used with
Projects with it also use handoff.
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.
MicrosoftSkillhandoff
Compact the current conversation into a handoff document for another agent to pick up.
Also in 3 projects that use this
Other versions22 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 22
- albertomarturelo/sii★ 18same name
- tornikebolokadze1-cyber/agent-foundation-kit★ 6same name
- ngmeyer/skills★ 4same name
- paureis/pau-skills★ 2same name
- PUNCKe/manuscript-context-integrity★ 2same name
- toper2525ua-eng/claude-longrun★ 2same name
- vardan6/trackline★ 2same name
- AN0099/toothpaste-kit★ 1same name
- CorvusWing/CorvusWing★ 1same name
- farky-tech/containers★ 1same name
12 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
- templates/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- templates/CLAUDE.mdCLAUDE.md
- session-openSkill
- workbench-scaffoldSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 18 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 19
Documents touched: Every document whose subject changed this session is updated now, not next time.
- Very specific: line 32
Run scripts/check. Fix every finding it reports before committing.
- Distinctive: line 38
Never commit on the default branch (main unless AGENTS.md says otherwise).
“Common” is measured: kept by at least 6 in 10 of the 18 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 close
A session that ends without capturing what it learned is unfinished. Walk every step; each item is either done or named in the hand-over.
1. Capture
- Decisions. Anything settled this session that changes how work is done goes
into
DECISIONS.md(or the logAGENTS.mdnames): what, why, how to apply. A decision that closes an issue cites its number. - Learnings. A gotcha that cost more than fifteen minutes becomes either a rule in
AGENTS.md(only if it changes behaviour, one line) or a note whereAGENTS.mdsays learnings live. Never a dated diary entry. - Documents touched. Every document whose subject changed this session is updated now, not next time. A doc that states how something works is a claim.
2. Rewrite the desk
Rewrite STATUS.md (or the desk file AGENTS.md names) from scratch: what is true
now, what is in flight and where, who owes what, the dates that matter, the open
questions. Delete finished and struck-through items; git keeps the history. Anything
longer than two lines moves to its own document with a link from the desk. Stay under
120 lines.
3. Check
Run scripts/check. Fix every finding it reports before committing; if a finding
cannot be fixed this session, say so in the hand-over rather than committing around
it. check: clean is the exit condition.
4. Commit on a branch
Never commit on the default branch (main unless AGENTS.md says otherwise). If the
session is still on it, cut a branch named for the issue or the track first. Commit
everything, work in progress included; the message names the track and references the
issue (Refs #N). Half-done work is committed as WIP, never left dangling in the
working tree.
5. Push and open a pull request
Push the branch and open a pull request against the default branch. The body states
what changed, what is still open, and which issue it closes or advances (Closes #N
or Refs #N); the tracker learns about the work from that reference, so nothing is
closed by hand. The maintainer merges; the session does not.
6. Hand over
Close with a short list: what landed (branch, PR), what was parked, what the next session should pick up first, and every item this session could not handle. No silent drops.
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.

