← ClaudeAtlas

checkpointlisted

Use when the context window is filling up (around 50% used) or before stepping away from a long session. Creates a handoff file that a fresh Claude Code session reads to resume without losing momentum.
cabaynes/charles-claude-skills · ★ 0 · AI & Automation · score 75
Install: claude install-skill cabaynes/charles-claude-skills
# /checkpoint — Context handoff before clearing The user is about to clear the context window and start fresh. Your job: capture **everything a new agent would need** so the next session loses no momentum. ## Step 1 — Read current state (parallel) Before writing anything, gather context. Run these in parallel: - `pwd` — where the session is rooted - `git status` and `git log --oneline -10` — if it's a git repo (skip silently if not) - `git diff --stat` — what's changed, uncommitted - Read the project-level `CLAUDE.md` if one exists in the CWD - Read `~/.claude/projects/<project-slug>/memory/MEMORY.md` to know which memory files exist - Check the current TodoWrite list state (if you have one in this session — recall from conversation, don't invent) - `echo "$CLAUDE_CODE_ENTRYPOINT"` — which surface this is. `cli` = terminal (standalone **or** VSCode's integrated terminal); anything else (or empty) = VSCode's visual-editor chat panel or another GUI surface. This decides the clear-context instructions in Step 5. Also pull from your conversation memory: - What was the user actually trying to accomplish in this session? - What did you finish? What's half-done? - What file paths and line numbers are you in the middle of? - What did you try that didn't work, and why? - Any decisions made with non-obvious rationale? - Any errors, blockers, or open questions waiting on the user? ## Step 2 — Update memory files Update auto-memory **only** for things that match the memory rules i