How this skill is triggered — by the user, by Claude, or both
Slash command
/claude-setup:checkpointThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Execute these steps in order:
Execute these steps in order:
Quickly evaluate:
git status --porcelain | head -10
If features.json exists and features were completed:
"status": "pass""status": "wip"If no features.json, skip this step.
Append a checkpoint entry to PROGRESS.md:
---
### Checkpoint: [YYYY-MM-DD HH:MM]
**Currently Working On:** [task description]
**Status:**
- [x] [Completed sub-task]
- [x] [Another completed sub-task]
- [ ] [Remaining sub-task]
**If Resuming:**
1. [Immediate next step]
2. [Key context to remember]
**Files Modified:**
- [file1.ts] - [what changed]
- [file2.ts] - [what changed]
Ask the user:
"Create a WIP commit? (Useful if you might switch branches or want a restore point)"
If yes:
git add -A
git commit -m "WIP: [current task] - checkpoint
Checkpoint at [time]. Work in progress, may not be complete.
Resume instructions in PROGRESS.md"
If no, skip the commit.
## Checkpoint Saved
**Current Task:** [description]
**Status:** [X of Y sub-tasks complete]
### To Resume
1. [Immediate next action]
2. [Key context]
3. [Any warnings or gotchas]
**Files touched this session:**
- [list of modified files]
**WIP Commit:** [yes - hash / no - changes uncommitted]
---
Checkpoint complete. Continue working or safely pause.
Checkpoints are useful for:
Checkpoints are lighter than session-end:
| Aspect | Checkpoint | Session End |
|---|---|---|
| Verification | Quick status | Full tests/types |
| Commit | Optional WIP | Required (if changes) |
| ROADMAP update | No | Yes |
| Intended for | Pause | Full stop |
| Time to run | ~30 seconds | ~2-5 minutes |
npx claudepluginhub matthewod11-stack/claude-setup --plugin claude-setupSaves and resumes state for multi-phase commands like /debug, /epic, /feature, /implement, and /plan, enabling work to survive session interruptions.
Creates a mid-session git commit and handoff note to save progress before risky changes, refactors, or task switches. Use instead of /wrap-up when continuing the session.
Saves session progress by committing changes, pushing to remote, creating/updating pull requests, persisting decisions/patterns to memory layers, compiling briefings, and archiving features. Use for checkpointing work or PRs.