CodeCannon checkpoint

Code Cannon: Commit and push WIP without review or merge

install

source · Clone the upstream repo

git clone https://github.com/LightbridgeLab/CodeCannon

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/LightbridgeLab/CodeCannon "$T" && mkdir -p ~/.claude/skills && cp -r "$T/.gemini/skills/checkpoint" ~/.claude/skills/lightbridgelab-codecannon-checkpoint-fd7b44 && rm -rf "$T"

manifest: .gemini/skills/checkpoint/SKILL.md

source content

Gemini CLI: This skill is triggered by description matching. State any arguments in your message. Sub-agent spawning is not supported — the automated review step in
/submit-for-review
must be done manually using the review-agent prompt in a separate session.

What

/checkpoint

does

/checkpoint

is a lightweight save point — commit and push work-in-progress to the remote without triggering type-checks, reviews, PR creation, or merge. Use it to persist progress during long coding sessions or before context-switching.

Step 1 — Verify branch

git branch --show-current

Protected branches (not a feature branch):

```
main
```
```
dev
```

If the current branch matches any of the above, abort immediately and say:

"You are on
<branch>
.
/checkpoint
must be run from a feature branch."

Step 2 — Check for changes

git status --porcelain

If the output is empty (no staged, unstaged, or untracked changes), say:

"Nothing to checkpoint — working tree is clean."

Stop. Do not create an empty commit.

Step 3 — Stage and commit

git add -A
git commit -m "WIP: <message>"

Commit message rules:

Always prefix with
```
WIP: 
```
so these commits are visually distinct in
```
git log
```
.

$ARGUMENTS

is provided, use it as

<message>

(e.g.

WIP: add auth middleware

If
```
$ARGUMENTS
```
is empty, auto-generate from the diff summary (e.g.
```
WIP: update auth.ts, add login tests
```
). Keep it under 72 characters.
Do not commit
```
.env
```
files, secrets, or build artifacts. If
```
git status
```
shows such files, add them to
```
.gitignore
```
or exclude them from staging before committing.

Step 4 — Push

git push -u origin HEAD

If the push fails because the remote branch does not exist yet, the

-u

flag handles creation. If it fails for another reason, report the error and stop.

Step 5 — Report

Count the files in the commit:

git diff --stat HEAD~1

Say:

"Checkpoint saved. N file(s) committed and pushed to
<branch>
. Run
/submit-for-review
when ready to open a PR."

Hard rules

Never create a PR.
Never trigger a review.
Never merge.
Never apply labels or modify issues.
Never run
```
make check
```
— checkpoints are not quality gates.
Do not prompt for confirmation —
```
/checkpoint
```
is a quick save, not a ceremony.