context-restore
Skill4 starsChanged 4 months agoMITView on GitHub
Resume a session from the latest (or a named) runtime/checkpoints/*.snapshot.md — reload the open threads and pending decisions, then re-orient them against the CURRENT context/state.md and digests/ (which may have moved on since the snapshot) and surface the deltas. Trigger on "restore context", "resume", "where were we", or the start of a continued session. Pairs with /context-save.
24 other projects use a version of this.
Adopted by
Most recently taken up by
- timurgaleev/vibestacktheir own version, first seen Nov 8, 2026
- jggomez/expert-ai-developer-skillstheir own version, first seen Nov 6, 2026
- torifo/skills-context-continuitytheir own version, first seen Oct 29, 2026
- trungtm78/ClaudeSkillstheir own version, first seen Oct 25, 2026
- thedigitalorganizer/soloshiptheir own version, first seen Oct 15, 2026
- ignavm1/claude-skillstheir own version, first seen Oct 13, 2026
Used with
Projects with it also use ios-clean, ios-fix and 6 more.
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.
Saqlain-811Skillios-clean
Remove the DebugBridge SPM package and all #if DEBUG wiring from an iOS app. (gstack)
Also in 5 projects that use this
Saqlain-811Skillios-fix
Autonomous iOS bug fixer. (gstack)
Also in 5 projects that use this
timurgaleevSkilldocument-generate
Generate missing docs for a feature, module or project as tutorials, how-tos, reference and explanation.
Also in 7 projects that use this
bastosSkillios-design-review
Review iOS app UI/UX design quality using Apple's design principles and the Liquid Glass-era design language from WWDC25/26. Use when asked for a design review, UX critique, visual design assessment, or evaluation of an app's interface quality, design intent, alignment with the new Apple design system, or usability. Triggers: "design review", "UX review", "visual design critique", "review the UI", "does this design work", "evaluate this interface", "design feedback", "Liquid Glass review".
Also in 5 projects that use this
johnlindquistSkilldiagram
Maintain and synchronize Unified Impact Diagrams following Diagram Driven Development (DDD) methodology. Create, update, and manage diagrams that connect user value to technical implementation.
Also in 4 projects that use this
SentrySkillspec
Produce a verified spec — problem, desired outcome, and acceptance criteria — before building. Use when given a GitHub/Linear issue link, when starting from a fuzzy in-conversation idea, or asked to "figure out what to do" / "scope this" / "what should I build" — whenever the *what* isn't yet pinned down. Grills the ambiguities, checks the premise against the code, and produces acceptance criteria you sign off on — then hands to design-first.
Also in 8 projects that use this
- +2 more from Saqlain-811
Other versions24 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 24
- garrytan/gstack★ 142ksame name
- jggomez/expert-ai-developer-skills★ 32same name
- timurgaleev/vibestack★ 8same name
- GTMify/claude-skills-starter★ 2same name
- HanksChen0110/skills★ 2same name
- chloropine/cgstack★ 1same name
- IyedBecheikh/bstack★ 1same name
- jpoindexter/theft-kit★ 1same name
- leishifu666/skills★ 1same name
- mahiunfiltered/claude-code-skills★ 1same name
14 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 repository16 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- llms-full.txtllms.txt
- llms.txtllms.txt
- agents-syncSkill
- call-agentSkill
- captureSkill
- context-saveSkill
- curatorSkill
- learnSkill
- onboardSkill
- recallSkill
- reviewSkill
- skillifySkill
- wiki-doctorSkill
- worklog-audioSkill
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 18 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 17
Default: the newest runtime/checkpoints/*.snapshot.md (sort by filename timestamp).
- Distinctive: line 22
Read the snapshot's open threads, pending decisions, and next action.
- Very specific: line 42
Follow superseded_by chains so you resume against current truth, not a frozen claim.
- Distinctive: line 43
Never restore secrets / credentials from a snapshot into the working context.
“Common” is measured: kept by at least 6 in 10 of the 18 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
Inherits references/kernel.md (the provenance contract). Reads references/wiki-spec.md for schema.
What this is
The other half of qcobrain's checkpoint pair. It rehydrates a /context-save snapshot and reconciles
it with reality — because the brain may have changed since the snapshot was taken. You get back the
thread state and a diff against current truth.
Execution
1 — Pick the snapshot
Default: the newest runtime/checkpoints/*.snapshot.md (sort by filename timestamp). If a name or
timestamp is given, use that one. If none exist, say so and offer to start fresh from context/state.md
digests/.
2 — Reload
Read the snapshot's open threads, pending decisions, and next action.
3 — Re-orient against current truth (the important part)
Re-read the current context/state.md, digests/, and the snapshot's referenced [[notes]]. Compute
the deltas:
- Threads the snapshot lists as open that are now resolved (closed in
state.md/decisions/log.md) → mark done. - Decisions that were pending and have since been logged in
decisions/log.md→ resolved. - Notes referenced by the snapshot that are now
status: superseded→ followsuperseded_byto current truth before reusing them. - Anything in
state.md/digests/newer than the snapshot → surface as "new since checkpoint".
4 — Hand back
Print: the goal, the still-open threads (post-reconciliation), the still-pending decisions, the recommended next action, and a short "changed since checkpoint" delta.
Guardrails (hard)
- Current truth beats the snapshot. On any conflict,
wiki/+context/state.mdwin; a snapshot is stale working memory, never a source. - Follow
superseded_bychains so you resume against current truth, not a frozen claim. - Never restore secrets / credentials from a snapshot into the working context.
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.

