session-closeout
Skill1 starsChanged 14 days agoNo licenceView on GitHub
Properly close out a Claude Code or Cowork session using a structured SOP that updates project documentation, commits work cleanly, captures session knowledge, and leaves the project folder in optimal state for the next session. Use this skill whenever the user says "close out", "wrap up", "wind down", "end session", "done for now", "that's it for today", "closeout", "session end", "park this", or any variation of finishing a work session. (A bare "save progress" mid-session belongs to session-checkpoint, not closeout.) Also trigger when the user issues a /closeout command. Even if the user just says "I'm done" or "let's stop here" — use this skill. Works in both Claude Code and Cowork. Designed to pair with the session-restart skill for clean handoffs between sessions.
- Reads credentials
- Deletes or force-pushes
- Commits and pushes
3 other projects use a version of this.
Adopted by
Most recently taken up by
- 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 versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- nino-chavez/agentic-ways-of-working★ 2same 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 repository14 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- apple-intelligenceSkill
- fleet-initSkill
- folder-forensic-auditSkill
- frontend-designSkill
- internal-commsSkill
- live-app-maintenanceSkill
- mac-mini-cleanupSkill
- project-kickoffSkill
- sai-process-sketchSkill
- security-baselineSkill
- session-checkpointSkill
- session-restartSkill
- xcode-cleanupSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
28 rules. 0 are common, 20 are distinctive, and 8 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
20
Distinctive
This author's own choices. Worth a look.
8
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 3 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.
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.