agentleFS
NoaiRoxNoaiRox/specialist-agent/skills/checkpoint/SKILL.md

checkpoint

Skill2 starsChanged 9 months agoMITView on GitHub

Use when about to start risky changes, before major refactors, or when you need a safe rollback point during multi-step implementations.

  • Deletes or force-pushes

91 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

8 rules. 0 are common, 8 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 85 edited versions we read keep these.

  • 8

    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
  1. Distinctive:

    Create, restore, list, or clean git checkpoints.

    line 11
  2. Distinctive:

    Before deleting or restructuring modules

    line 18
  3. Distinctive:

    Before running destructive git operations

    line 20
  4. Distinctive:

    NOT for: every small edit (too noisy)

    line 21
  5. Distinctive:

    Commit with checkpoint message

    line 33
  6. Distinctive:

    Remove all checkpoint tags (keeps restore points).

    line 133
  7. Distinctive:

    Remove ALL checkpoints and restore points.

    line 152
  8. Distinctive:

    If no argument provided:

    line 161

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

/checkpoint - Git Checkpoint Management

Create, restore, list, or clean git checkpoints.

Command: $ARGUMENTS

When to Use

  • About to start a risky refactoring
  • Before deleting or restructuring modules
  • During multi-step implementations (checkpoint between steps)
  • Before running destructive git operations
  • NOT for: every small edit (too noisy)

Operations

Create Checkpoint

/checkpoint create feature-auth

Workflow:

  1. Stage all changes
  2. Commit with checkpoint message
  3. Create tag
git add -A
git commit -m "checkpoint: [name]"
git tag checkpoint/[name]

Output:

──── Checkpoint Created ────
Name: checkpoint/feature-auth
Commit: abc1234
Files: 5 changed
Time: 2024-01-15 14:30:22

Create Restore Point

/checkpoint restore-point

Creates a timestamp-based restore point before major operations.

git tag restore-point/$(date +%Y%m%d-%H%M%S)

Output:

──── Restore Point Created ────
Tag: restore-point/20240115-143022
Use to rollback entire session if needed.

List Checkpoints

/checkpoint list
git tag -l "checkpoint/*" | sort -V
git tag -l "restore-point/*" | sort

Output:

──── Checkpoints ────
Checkpoints:
  checkpoint/task-1        (2024-01-15 14:20)
  checkpoint/task-2        (2024-01-15 14:25)
  checkpoint/feature-auth  (2024-01-15 14:30)

Restore Points:
  restore-point/20240115-141500
  restore-point/20240115-143022

Restore Checkpoint

/checkpoint restore feature-auth

Warning: This will discard uncommitted changes!

# Confirm with user first
git reset --hard checkpoint/[name]

Output:

──── Checkpoint Restored ────
Restored to: checkpoint/feature-auth
Commit: abc1234
Current state matches checkpoint.

Full Rollback

/checkpoint rollback 20240115-143022

Rollback to a restore point (undoes all work since).

git reset --hard restore-point/[timestamp]

Clean Checkpoints

/checkpoint clean

Remove all checkpoint tags (keeps restore points).

git tag -l "checkpoint/*" | xargs -n 1 git tag -d

Output:

──── Checkpoints Cleaned ────
Removed: 5 checkpoint tags
Kept: 2 restore points

Clean All

/checkpoint clean-all

Remove ALL checkpoints and restore points.

git tag -l "checkpoint/*" | xargs -n 1 git tag -d
git tag -l "restore-point/*" | xargs -n 1 git tag -d

Default Behavior

If no argument provided:

/checkpoint

Creates a timestamped checkpoint:

checkpoint/auto-20240115-143022

Usage in Workflow

Before Risky Changes

/checkpoint restore-point
# Make risky changes
# If it fails:
/checkpoint rollback [timestamp]

During Feature Development

/checkpoint create step-1
# Work on step 2
/checkpoint create step-2
# If step 2 is wrong:
/checkpoint restore step-1

After Session

/checkpoint clean  # Remove task checkpoints
# Keep restore points for safety

Output

──── /checkpoint ────
Operation: [create|restore|list|clean]
[Operation details]

Anti-Rationalization

ExcuseReality
"I don't need a checkpoint, it's a small change"Small changes break things too. A checkpoint takes 2 seconds, a rollback without one takes hours.
"Git history is enough"Checkpoints are labeled save points - faster than hunting through git reflog.
"I'll just undo if something goes wrong"You can't undo what you can't identify. Checkpoints mark the exact safe state.

Rules

  1. Always confirm before restore - Destructive operation
  2. Create restore point before major work
  3. Clean checkpoints after successful completion
  4. Keep restore points until merge

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.