Checkpoint
Claude Code skills for researchers, by a researcher. Humans + agents exploring what hasn't been built yet — without losing alignment along the way.
npx -y skills add ajaygunalan/flow-friction --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.
- 2 stars2 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
Mark a human-verified milestone — summarizes work since last checkpoint, creates an empty checkpoint commit, pushes
SKILL.md
1.5 KB, as published. Nobody here has run it
Anything uncommitted?
Check git status -s. If there are uncommitted changes (user hand-edits), stage all and commit them as a regular commit before proceeding. Then continue to the checkpoint.
What happened since last checkpoint?
Last checkpoint:
!`git log --grep="^checkpoint:" -1 --format="%H %s" 2>/dev/null || echo "(none)"`
Branch: !`git branch --show-current`
Find the last checkpoint: commit hash. If none exists, use the merge-base with the default branch (git merge-base HEAD main 2>/dev/null || git merge-base HEAD master 2>/dev/null || git rev-list --max-parents=0 HEAD).
Show all commits since that baseline:
git log <baseline>..HEAD --oneline
Show the diff summary:
git diff <baseline>..HEAD --stat
Read the diffs and understand what changed.
Why did it change?
Understand the purpose from the diffs and conversation context. This informs the checkpoint message.
What do we call it?
Present 4 options via the ask_user_question tool: same intent, four distinct phrasings. Each captures the work from a fresh angle — different words, different rhythm, different emphasis. User picks or writes their own.
Create an empty commit:
git commit --allow-empty -m "checkpoint: <chosen message>" -m "Tested-by: $(git config user.name)"
Push
git push and verify with git status.