reboot
Skill0 starsChanged 2 months agoMITView on GitHub
Write the handoff, then restart with fresh context resuming from it. Use when the user says /reboot, "handoff and restart", "clear and continue", "restart with fresh context".
2 other projects use a version of this.
Adopted by
Most recently taken up by
- tonydzi/second-brain-starter-kittheir own version, first seen Sep 8, 2026
- ignatovv/VibePadtheir own version, first seen Feb 12, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- ignatovv/VibePad★ 67same name
- tonydzi/second-brain-starter-kit★ 6same 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 repository20 other files it gives its agents.
- agent-harness-constructionSkill
- claudex-loopSkill
- click-path-auditSkill
- context-budgetSkill
- councilSkill
- deploy-projectSkill
- dreamSkill
- loop-design-checkSkill
- regex-vs-llm-structured-textSkill
- rules-distillSkill
- scrapling-officialSkill
- session-auditSkill
- shinen-designSkill
- skillspectorSkill
- skill-stocktakeSkill
- token-budgetSkill
- vault-indexSkill
- vault-ingestSkill
- vault-lintSkill
- vault-querySkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
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
- Very specific: line 10
Write/update the handoff doc exactly as the handoff skill specifies (Goal, Current Progress, What Worked, What Didn't Work, Next Steps).
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
One command: handoff → clear → resume.
Steps:
- Write/update the handoff doc exactly as the
handoffskill specifies (Goal, Current Progress, What Worked, What Didn't Work, Next Steps). Save asHANDOFF.mdin the project root, or update the existing one. Arm the resume by writing the absolute handoff path to
~/.claude/.reboot-pending:printf '%s\n' "<abs path to HANDOFF.md>" > ~/.claude/.reboot-pending- Tell the user, in one line:
Handoff written: <path>. Now run /clear — I will resume from it on my own.
Then stop. Do not start new work in this context.
On the next session the SessionStart hook (matcher clear) reads .reboot-pending, injects the handoff path as context, and deletes the file — so the fresh session picks the work back up automatically.
/clear cannot be typed by the agent; that keystroke stays with the user. Everything around it is automatic.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.