Checkpoint
Skill hereinthehive/kickstart/.claude/skill-templates/checkpoint
A Claude Code starter — fork, run /onboarding, and Claude sets itself up for your project
npx -y skills add hereinthehive/kickstart --skill checkpointAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Save a recoverable snapshot of the current working tree via git stash. Triggered by /checkpoint or "save a checkpoint" / "snapshot this".
SKILL.md
2.0 KB, as published. Nobody here has run it
You are the /checkpoint skill. Save a recoverable snapshot before something risky.
Triggers
- Slash form:
/checkpoint [optional description] - Natural language: "save a checkpoint", "snapshot this", "before we do that, save where we are"
Step 1: Hard refusals (check first)
- No git repo.
git rev-parse --is-inside-work-tree 2>/dev/null— if not, tell user the safety net wasn't activated; abort. - Merge in progress.
git rev-parse --verify MERGE_HEAD 2>/dev/null— if exits 0:"Something's mid-merge here — let's not checkpoint until that's resolved."
Step 2: Infer a description
If the user passed a description, use it. Otherwise, infer one from recent activity:
- The last 1-2 things you helped with (e.g., "before refactoring login form").
- Fall back to a timestamp if nothing distinctive: "checkpoint at <time>".
Step 3: Stash with the description
git stash push -u -m "checkpoint: $(date -u +%Y-%m-%dT%H:%M:%SZ) <description>"
Step 4: Log it
Append to .claude/checkpoints.log (create if missing):
<ISO timestamp> | <description> | <stash ref returned by git stash list -1>
Step 5: Confirm
"Saved a checkpoint: '<description>'. If you want to come back to this exact state, just say 'restore the checkpoint' or pop the stash."
Restoration
Triggered by "restore the checkpoint" or "go back to the checkpoint":
If multiple checkpoints exist (read .claude/checkpoints.log), list and ask which.
git stash apply stash@{N}
Note: use apply rather than pop so the checkpoint stays available for repeated restoration.
Hard rules
- Never overwrite a checkpoint silently. Always create a new stash entry.
- Never delete a checkpoint without explicit user confirmation.
- The
.claude/checkpoints.logis append-only from this skill's perspective.