agentleFS
simscalsimscal/sapiens-dtj/.claude/skills/checkpoint/SKILL.md

checkpoint

Skill0 starsChanged 4 months agoMITView on GitHub

Use at workflow entry (read + resume prompt) and after each step completes (write). Owns workflow resume state under `.claude/state/<workflow>.json` — the single source of truth for resume across feature, bugfix, refactor.

93 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use aside, spinoff and 10 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.
  • TheKREATORSSkill

    aside

    Answer a quick side question without interrupting or losing context from the current task. Resume work automatically after answering.

    Also in 3 projects that use this

  • AhmedMerzaSkill

    spinoff

    After a branch is finished, harvest the work it made CHEAP — the helper you wrote that four other sites now hand-roll, the plumbing that turned a deferred feature small, the pattern that just split the codebase in two. Produces a follow-up backlog (0–3 candidates, feeding /issue), NEVER commits on the current branch. Invoke with /spinoff at the tail of the chain — after /fix-review has settled the review findings, before the MR merges — or when the user asks \"what else should we do while we're here / what did this unlock / anything to follow up on\". This is ship-check's optional twin — that finds what's MISSING and blocks the merge; this finds what's now CHEAP and blocks nothing. Restraint-gated: \"nothing spun off\" is the common and correct answer, and a finding that would have been equally valid before this branch is not a finding.

    Also in 3 projects that use this

  • TheKREATORSSkill

    instinct-export

    Export instincts from project/global scope to a file

    Also in 3 projects that use this

  • seek888Skill

    open-gstack-browser

    Launch GStack Browser — AI-controlled Chromium with the sidebar extension baked in. Opens a visible browser window where you can watch every action in real time. The sidebar shows a live activity feed and chat. Anti-bot stealth built in. Use when asked to "open gstack browser", "launch browser", "connect chrome", "open chrome", "real browser", "launch chrome", "side panel", or "control my browser". Voice triggers (speech-to-text aliases): "show me the browser".

    Also in 5 projects that use this

  • diego-tobalinaSkill

    build-fix

    Fix build and compilation errors systematically. Run when build fails.

    Also in 5 projects that use this

  • seek888Skill

    design-html

    Design finalization: generates production-quality Pretext-native HTML/CSS. Works with approved mockups from /design-shotgun, CEO plans from /plan-ceo-review, design review context from /plan-design-review, or from scratch with a user description. Text actually reflows, heights are computed, layouts are dynamic. 30KB overhead, zero deps. Smart API routing: picks the right Pretext patterns for each design type. Use when: "finalize this design", "turn this into HTML", "build me a page", "implement this design", or after any planning skill. Proactively suggest when user has approved a design or has a plan ready. (gstack) Voice triggers (speech-to-text aliases): "build the design", "code the mockup", "make it real".

    Also in 5 projects that use this

  • +2 more from TheKREATORS
  • +2 more from seek888

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 1 is distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 87 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read .claude/state/<workflow>.json (absent → null), validate _version, return the entry at <run-key> or null.

    line 46
  2. Distinctive:

    Write back with 2-space indent.

    line 55
  3. Very specific:

    After each step, checkpoint:write with step = next step's label (or "done" after the final step), plus decisions + artifacts produced in …

    line 91
  4. Very specific:

    Write final state with current_step = "done", current_phase = "done".

    line 95

“Common” is measured: kept by at least 6 in 10 of the 87 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

File Layout

.claude/state/
  feature.json
  bugfix.json
  refactor.json

Schema

{
  "_version": 1,
  "<run-key>": {
    "stage": "<stage-name>",
    "primary_arg": "<value>",
    "current_phase": "<phase-id>",
    "current_step": "<step-label>",
    "started": "<iso8601>",
    "updated": "<iso8601>",
    "completed_steps": ["step-1", "step-2"],
    "phases": {
      "<phase-id>": {
        "decisions": { "key": "value" },
        "artifacts": { "issues": [], "branches": [], "files": [] }
      }
    }
  }
}
  • _version = 1. Halt with "checkpoint schema version mismatch: file=<v> expected=1" on mismatch.
  • <run-key> = <stage>-<primary-arg>.
  • completed_steps is append-only and ordered.
  • Decision keys must be stable identifiers (e.g. stack_choice), not question text.

Read

Read .claude/state/<workflow>.json (absent → null), validate _version, return the entry at <run-key> or null.

Write

Inputs: workflow, run_key, stage, primary_arg, phase, step, optional decisions, optional artifacts.

  • Initialise the run-key entry if absent (stage, primary_arg, started, empty completed_steps/phases).
  • Deep-merge decisions + artifacts into phases[phase] (arrays append + dedupe).
  • Set current_phase, current_step (the next step), updated; append the previously-current step to completed_steps if not already there.
  • Write back with 2-space indent.

Clear

Inputs: workflow, run_key. Delete obj[run_key]; if only _version remains, rm the file, else write back. Absent file → no-op.

List

Inputs: workflow. Return keys except _version, sorted by updated desc (absent file → []).

Resume Prompt

On checkpoint hit at workflow entry, always ask via AskUserQuestion:

Found checkpoint for <workflow> <run-key>:
  Stage:    <stage>
  Started:  <started>
  Last:     <updated> (<current_step>)
  Done:     step-1 → step-2 → step-3
  Next:     <next step from mode file>

Resume? [Y]es / [r]estart / [c]ancel
  • Resume → load decisions/artifacts, jump to the step after current_step.
  • Restart → checkpoint:clear, start from the beginning.
  • Cancel → abort; leave the checkpoint untouched.

Replay

  • Decisions — before every AskUserQuestion, reuse phases[<phase>].decisions[<key>] if present; else ask and checkpoint:write the answer.
  • Artifacts — before creating any issue/branch/file, reuse an existing reference in phases[<phase>].artifacts if present; else create and checkpoint:write.

Step Boundary

After each step, checkpoint:write with step = next step's label (or "done" after the final step), plus decisions + artifacts produced in the step just completed.

On Completion

Write final state with current_step = "done", current_phase = "done". Stage terminates the workflow (a release stage) → checkpoint:clear all run-keys for the same sprint/issue. Otherwise leave the checkpoint in place.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.