session-closeout
Skill1 starsChanged 23 days agoMITView on GitHub
'Before ending a session: reconcile changed files, update docs and changelog,
4 other projects use a version of this.
Adopted by
Most recently taken up by
- Brandondaymdr/Claude-Skillstheir own version, first seen Oct 29, 2026
- nino-chavez/agentic-ways-of-workingtheir own version, first seen Oct 13, 2026
- seheim-commits/claude-skillstheir own version, first seen Jun 3, 2026
- seco/declawtheir own version, first seen Apr 4, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- nino-chavez/agentic-ways-of-working★ 2same name
- Brandondaymdr/Claude-Skills★ 1same name
- seco/declaw★ 1same name
- seheim-commits/claude-skills★ 0same name
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 repository46 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .codex/AGENTS.mdAGENTS.md
- .gemini/AGENTS.mdAGENTS.md
- .cursor/rules/agent-foundry-orchestrator.mdcCursor rule
- .cursor/rules/agent-foundry-skills.mdcCursor rule
- web/llms.txtllms.txt
- anti-slopSkill
- api-designSkill
- automation-pickSkill
- bottleneck-gatingSkill
- budget-guardSkill
- cache-identitySkill
- constraint-then-solveSkill
- context-optimizationSkill
- cron-troubleshootSkill
- e2e-test-strategySkill
- engram-routingSkill
- execution-observabilitySkill
- fallback-model-routingSkill
- feedback-loopSkill
- judge-integritySkill
- knowledge-extractSkill
- landscape-firstSkill
- measure-firstSkill
- plan-before-codeSkill
- plan-then-actSkill
- prompt-disciplineSkill
- pushback-when-wrongSkill
- quality-protocolSkill
- read-before-buildSkill
- re-verify-findingsSkill
- session-distillSkill
- show-your-workSkill
- structured-output-contractSkill
- verify-firstSkill
- workflow-decomposeSkill
- agent-memory-vaultSkill
- agent-team-standardsSkill
- autonomous-briefingSkill
- book-to-skillSkill
- chrome-devtools-mcp-bridgeSkill
- design-languageSkill
- funnel-pr-guardSkill
- persistent-memorySkill
- sql-migration-trioSkill
- token-compressionSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
2
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 31
If a surface isn't applicable, tag it n/a — don't fabricate evidence.
- Distinctive: line 57
Do the closeout. The cost is 2 minutes.
- Very specific: line 77
Every exit path writes a terminal status: completed, failed, or interrupted.
- Distinctive: line 79
Check that every output reference resolves before closeout.
“Common” is measured: kept by at least 6 in 10 of the 4 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 Closeout
A session that ends without closeout is work that has to be redone. Apply at the end of any multi-step project, before /reset, before stopping for the day, or before handing to someone else.
Procedure
The 6 surfaces
Reconcile each before declaring done. Tag with status: verified / pending / not-applicable.
| Surface | Question | Evidence |
| Code | What did we actually change? | git diff + tests passing |
| Runtime | Does it actually work? | Live URL, deployed artifact, manual test |
| Docs | Can a new person understand what we built? | README, changelog, inline comments |
| Rules | Are the constraints the next session will see still correct? | CLAUDE.md / hooks |
| Memory | Is there anything the next session should know that isn't in code or docs? | Note to self, vault entry |
| Workspace | Any untracked files, stale branches, temp dirs? | git status clean, no .tmp |
If a surface isn't applicable, tag it n/a — don't fabricate evidence.
The handoff note
End every multi-step session with a handoff. Format:
## Handoff — <date>
**Done:** [list of completed work, with PR/branch links]
**In progress:** [what was started but not finished]
**Loose ends:** [bugs, tech debt, follow-ups]
**Decisions:** [non-obvious choices and why]
**Next steps:** [what to do first next session, in order]Save it: commit to the repo, paste it as the session's last message, both.
When to skip
- Single-question Q&A
- Throwaway experiments
- Sessions that produced nothing (deleted the work, no code change)
When in doubt
Do the closeout. The cost is 2 minutes. The cost of NOT doing it is the next session starting from zero.
Anti-patterns
- Ending with "done" while work sits uncommitted or untested.
- Fabricating evidence for a surface that was not checked.
- Deleting artifacts instead of recording retention.
- Leaving a
runningstatus as a permanent state.
Verification Checklist
- All six surfaces are tagged verified, pending, or n/a.
- Runtime behavior was checked, not inferred.
- Handoff note has done, in-progress, loose ends, next steps.
- Every output reference resolves.
- Workspace has no unexplained untracked or temp files.
Terminal State
- Every exit path writes a terminal status: completed, failed, or interrupted. A crash must leave
runningas an unambiguous signal, not a permanent lie. - Repair stale
runningrows at startup with an explicit age threshold. - Check that every output reference resolves before closeout; a dangling locator is a data-loss report.
- Recompute derived aggregates only after the terminal write, and record the config fingerprint used.
- Closeout is not deletion: keep summaries and artifact references, drop only what retention policy names.
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.

