end
Skill1 starsChanged 4 months agoMITView on GitHub
Close a chat all-in-one — run /wrapup then /handoff back-to-back, so finalizing the work and saving the resume context is one command. The closing bookend to /start. Use when the user says "/end", "end", "close this out", "wrap up and hand off", or "I'm done, save it".
10 other projects use a version of this.
Adopted by
Most recently taken up by
- chris-peterson/tacktheir own version, first seen Oct 26, 2026
- aalishan001/opencockpittheir own version, first seen Oct 25, 2026
- onblueroses/stratatheir own version, first seen Oct 18, 2026
- pche-broken-artist/forge-of-thoughttheir own version, first seen Oct 13, 2026
- jantichy/claudetheir own version, first seen Oct 13, 2026
- conorbronsdon/agent-context-ostheir own version, first seen Oct 8, 2026
Used with
Projects with it also use update.
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.
AnthropicSkillupdate
Sync tasks and refresh memory from your current activity. Use when pulling new assignments from your project tracker into TASKS.md, triaging stale or overdue tasks, filling memory gaps for unknown people or projects, or running a comprehensive scan to catch todos buried in chat and email.
Also in 3 projects that use this
Other versions10 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 10
- jantichy/claude★ 45same name
- conorbronsdon/agent-context-os★ 30same name
- pche-broken-artist/forge-of-thought★ 12same name
- onblueroses/strata★ 3same name
- aalishan001/opencockpit★ 2same name
- bastndev/skills★ 2same name
- conorbronsdon/agent-workspace★ 2same name
- alectivism/maven-template★ 1same name
- chris-peterson/tack★ 0same name
- torarnv/claude-project-manager★ 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 repository9 other files it gives its agents.
- commitpushSkill
- discordembedSkill
- discordmsgSkill
- handoffSkill
- prettyhtmlSkill
- prettymsgSkill
- startSkill
- wrapupSkill
- wtfSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.
0
Common
Most of the 9 edited versions we read keep these.
1
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 29
Run the full /wrapup checklist, reporting each item ✅/⏭️/⚠️.
- Very specific: line 36
Don't commit/push unless explicitly asked (that gate lives in /wrapup).
- Distinctive: line 37
Don't skip the wrapup checks and jump straight to the handoff — finalize first.
“Common” is measured: kept by at least 6 in 10 of the 9 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
/end — close the chat all-in-one (wrapup → handoff)
The closing bookend to /start. Runs the two closing skills back-to-back, in the right order, with
one combined summary — so closing a session is a single command instead of two manual steps.
/start <topic> ──work──► /commitpush (mid-session) ──► /end ──► /clear
(open) (close)/wrapup— finalize the work product: build/lint/test green, version/changelog if the project uses one, docs, and a gated commit (only if the user asks). See the/wrapupskill for the full checklist./handoff— write the throwaway resume doc capturing where the work is + what's left so a fresh chat can pick up after a/clear. See the/handoffskill.
Why both, in this order
/wrapup finalizes the code; /handoff preserves the chat. Wrapup first (so the handoff
describes the finalized state), handoff last. Run them individually if you only want one half.
Steps
- Run the full
/wrapupchecklist, reporting each item ✅/⏭️/⚠️. Commit stays gated — don't commit/push unless the user asked. - Then run
/handoff— write the resume doc to the handoffs folder (destination, not journey). - Print one combined summary: what wrapup finalized + the handoff doc's path, and a "safe to
/clear— next time run/start" line.
Don'ts
- Don't commit/push unless explicitly asked (that gate lives in
/wrapup). - Don't skip the wrapup checks and jump straight to the handoff — finalize first.
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.