Menu
Save active session context, git state, recent commits, and next steps to one tracking issue before compaction or handoff.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
When stuck on a specific problem, stop coding, gather context, and ask /deep or /pro for a fresh perspective.
Reframe recurring or wrong-shaped problems into a design where the bug cannot happen.
Run 5 Whys plus /big reframing to trace a symptom to structural root cause before fixing.
Batch operations across files with confidence-based auto-apply. Use for renaming, search-replace, refactoring code, updating text/markdown, migrating terminology, and API migrations. Run `bun tools/refactor.ts --help` for detailed command reference.
Analyze a decision end-to-end: gather context, compare options, score tradeoffs, and present one clear recommendation.
Pause implementation for architecture or understanding discussion, checkpoint context, then resume with captured decisions.
| name | checkpoint |
| effort | max |
| description | Save active session context, git state, recent commits, and next steps to one tracking issue before compaction or handoff. |
| argument-hint | [message] |
Keywords: checkpoint, compact, resume, context
Save session context to a single tracking issue (in whichever tracker the project uses) so it survives compaction and can be recovered by the next session or post-compact continuation.
Argument: $ARGUMENTS
Look for an existing in-progress issue that serves as the session's tracking issue. Prefer:
If you're reusing an existing tracking issue whose first paragraph is missing/weak/stale relative to the session's actual focus, refresh it before appending the checkpoint notes below.
There must be exactly ONE tracking issue. If multiple candidates exist, pick the one most relevant to the current work.
IMPORTANT: The tracking issue must be claimed by this session so the pre-compact hook can find it.
Collect ALL of these:
git status --short | head -20git log --oneline -10git branch --show-currentUpdate the tracking issue with structured notes. The first line MUST be the RESUME directive — this is what post-compact agents see first:
RESUME: <recover-command-for-your-tracker> <ISSUE_ID>
After compact, run the command above FIRST. Do not list all issues or start new work.
## Session Checkpoint
**Session:** <session-id>
**Branch:** <branch>
**Time:** <timestamp>
### What was done
<1-3 bullet summary of session work>
### Active issues
<list of in-progress issues with titles>
### Open issues (created this session)
<any new issues that need future work>
### Recent commits
<last 10 commits>
### Uncommitted changes
<git status>
### Next steps
<what should be picked up next — be specific>
<reference file paths, issue IDs, function names>
### Key context
<anything that would be lost in compaction — design decisions, failed approaches, gotchas>
If the user provided an argument (message), include it as the primary "Next steps" content.
Tell the user:
Multiple sessions share the same repo. The tracking issue is identified by a "claimed by current session" marker. The pre-compact hook searches for issues claimed by the current session — if the issue isn't claimed, the hook can't find it and context is lost.
This skill runs automatically via the pre-compact hook when the user types /compact.
It can also be invoked manually with /checkpoint at any time.
/merge — orthogonal axis. /checkpoint preserves narrative for resume; /merge integrates work back to main. They compose: /checkpoint before /compact, /merge before stopping the workday./complete — different question. /complete audits whether the work is finished; /checkpoint saves the context whether or not it's finished./discuss — /discuss checkpoints to the tracking issue automatically when entering discussion mode; uses the same machinery./recall — recovers checkpoint content in a future session by ID.