pause
Skill1 starsChanged 3 days agoMITView on GitHub
Stop everything cleanly in the middle of a task so that it can go on later - no new step started, the step under way brought to a consistent state (never a file half edited or a build left broken), every background job / monitor / subagent / workflow / build / loop / scheduled wake-up started for the task stopped, nothing committed or pushed that the rules of the user do not allow, then a checkpoint written (goal, rules, done, interrupted, the exact next steps, what was stopped and how to start it again, files changed, decisions) and one short message - the work resumes at the next "continue" (continue-work). Use whenever the user says /pause, "stop tout proprement", "arrête-toi proprement", "mets en pause", "on reprendra plus tard", "stop et reprends au prochain continue", "pause the work", "stop cleanly".
17 other projects use a version of this.
Adopted by
Most recently taken up by
- aaroncohn/babysittertheir own version, first seen Nov 16, 2026
- finolabs/finolabs-vibecodetheir own version, first seen Nov 16, 2026
- finolabs/vibecodetheir own version, first seen Nov 15, 2026
- aaroncohn/openspec-conductor-powerupstheir own version, first seen Nov 8, 2026
- Dariusplayer09/adaptive-skillstheir own version, first seen Nov 8, 2026
- DerAlo/ari-auto-pacingtheir own version, first seen Nov 1, 2026
Used with
Projects with it also use resume and init.
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.Other versions17 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 17
- alexknowshtml/claude-skills★ 144same name
- wrg32786/aigent-os★ 26same name
- kennethleungty/claude-music★ 23same name
- maxwellsdm1867/wheeler★ 12same name
- finolabs/finolabs-vibecode★ 4same name
- finolabs/vibecode★ 4same name
- Jhonnyr97/JevGuard★ 2same name
- stepanenkoviktor0110-boop/ai-dev-methodology★ 2same name
- aaroncohn/babysitter★ 1same name
- aaroncohn/openspec-conductor-powerups★ 1same name
7 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 repository70 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- ask-at-endSkill
- clarifySkill
- continue-workSkill
- exportSkill
- full-permissionSkill
- ideationSkill
- interactive-questionsSkill
- onboardSkill
- presentationSkill
- rtkSkill
- setup-contextSkill
- write-like-meSkill
- audit-bugsSkill
- audit-depsSkill
- audit-qualitySkill
- audit-securitySkill
- benchmarkSkill
- cmake-styleSkill
- cpp-classSkill
- cpp-commentsSkill
- cpp-projectSkill
- cpp-styleSkill
- better-explain-docSkill
- better-html-docSkill
- better-html-styleSkill
- better-protocol-docSkill
- docs-updateSkill
- explain-docSkill
- html-docSkill
- html-styleSkill
- protocol-docSkill
- readme-styleSkill
- reportSkill
- wiki-styleSkill
- ci-cdSkill
- git-commitSkill
- git-conventionsSkill
- pre-commitSkill
- legal-checkSkill
- legal-setupSkill
- licenseSkill
- libutils-exceptionSkill
- libutils-installSkill
- libutils-setupSkill
- libutilsSkill
- python-classSkill
- python-commentsSkill
- python-projectSkill
- python-styleSkill
- auditSkill
- cppSkill
- devSkill
- docSkill
- gitSkill
- legalSkill
- pythonSkill
- setup-projectSkill
- styleSkill
- setup-studioSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 15 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 22
No question to the user (the popup included): what would need an answer goes in the checkpoint.
- Distinctive: line 25
Only what this session started for the task, never a process of the user:
- Distinctive: line 35
Commit or push only what the rules of the user already allow for this repository (a project rule granting commits after each batch: commit …
“Common” is measured: kept by at least 6 in 10 of the 15 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
Pause: stop cleanly, resume at the next "continue"
SKILL_DIR = the directory of this file. The user wants the work stopped now, cleanly, and taken up again later
by a plain continue (the continue-work skill), in this session or a later one, without re-explaining anything.
It is not a handover to another machine or model (that is export), and not the end of the task.
1. Stop starting things
- From now on, start no new step: no new edit, command, build, agent or question.
- The step under way is brought to the nearest consistent state, the shortest way:
- a file edit in progress: finish it so the file is valid (syntax, matching blocks), or put the file back as it was before the step; never leave a file half written;
- a change spread over several files (a rename, an API change): finish it if it is a few edits, otherwise revert the part of this step and note it in the checkpoint as not started;
- a long command (build, test run, download): stop it (below) rather than wait, unless it ends within a minute.
- No question to the user (the popup included): what would need an answer goes in the checkpoint.
2. Stop what runs for the task
Only what this session started for the task, never a process of the user:
- background shell commands and monitors:
TaskStopeach one still running; - subagents, forks, workflows:
TaskStop(a workflow keeps its run id: note it, it can be resumed); - a
/looprunning:ScheduleWakeupwithstop: true; crons created for the task:CronDelete; - processes it launched outside the task tools (a server, a build in another folder): stop them by their exact
command line (
pgrep -fato check first), never a broadpkill; - a temporary branch or worktree it made: leave it, write its path in the checkpoint (never delete work). For each one, note how to start it again (the command), or that it is not needed any more.
3. Leave the repository as the rules say
- Commit or push only what the rules of the user already allow for this repository (a project rule granting commits after each batch: commit the finished part, never a half step). Otherwise nothing is committed: the changes stay in the working tree and are listed in the checkpoint.
- Nothing destructive to "clean up" (no
git reset, no deleted file the user did not ask to delete).
4. Write the checkpoint
bash SKILL_DIR/scripts/checkpoint.sh path # the file of this project (~/.claude/pauses/<project>.md)Fill templates/checkpoint.md into that file (one per project, a new pause replaces the old one), terse like rtk
(facts, one per line, no prose), every path and command exact:
- the goal in the user's words, the rules that apply (git, language, style, what needs a confirmation);
- done (verified how), interrupted (its exact state), next in order - the first item is what
continueruns first; - what was stopped and how to restart it, the files changed and not committed, the temp files, decisions, open points. A secret is never written in it (a token, a key, a password: say where it comes from instead).
5. Answer and stop
One short message in the user's language, then no more tool call:
En pause.+ what was stopped (one line), the state of the step under way, where the checkpoint is;Dis « continue » pour reprendre à : <next step>.Other checkpoints waiting on this computer:checkpoint.sh list.
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.

