← ClaudeAtlas

checkpointlisted

Commit and push pending work, then either continue to the next backlog step (context still healthy) or emit a paste-ready resume prompt plus a recommended relaunch model + reasoning effort for a fresh session (context tight). Use when the user says "checkpoint", "commit and continue", "wrap this step up", or asks whether to keep going vs. clear context.
jrittelmeyer/ai-dev-kit · ★ 1 · AI & Automation · score 74
Install: claude install-skill jrittelmeyer/ai-dev-kit
# checkpoint Commit + push whatever is pending, then decide: continue to the next step in this session, or hand off cleanly with a resume prompt. Never do half of both. Adapter: `.claude/ai-dev-kit.config.json` (`commit`, `ci`, `cache`, `docs`); a missing field → derive it from the repo and say so. ## 1. Commit & push - `git status` first; stage only the files that belong to the finished work (no blind `git add -A` if anything unrelated is dirty). If the tree is clean, say so and go to step 2. - Message: conventional style matching `git log` (`feat(web): …` / `chore: …`), body = what/why + one-line verification note. Respect the adapter's `commit` block: `trailers: false` means **no `Co-Authored-By` trailers**; `useFileFlag: true` means write the message to a scratchpad file and `git commit -F <file>` (inline `-m` quoting breaks on PowerShell 5.1). - Push. **If this checkpoint ends the session** (step 2 says hand off), watch CI to green now — provider recipes (find the run for this exact sha → watch → confirm the conclusion via a JSON query, never the stream alone) are in [references/ci-watch.md](references/ci-watch.md), keyed on the adapter's `ci.provider`. If instead you're continuing with more work that ends in its own watched CI run, one watch at the end covers the tree. - **Housekeeping (after push):** run the adapter's `cache.prune` command if defined — local build caches often have no TTL or size cap and grow by gigabytes per build, so pru