← ClaudeAtlas

checkpointlisted

Prepare for context compaction by hand, with care, before you run /compact. A deliberate, model-driven pass that brings ALL durable context up to date so nothing is left stale anywhere: flushes the Session Ledger, syncs the plan file, carries what outlives the task into the project state file, graduates cross-project lessons into the memory store, reconciles project knowledge docs, refreshes the current situation (a /update-style "where we are, what's next"), guards against context bloat, and only then gives a green light to compact. It never compacts by itself. It exists because automatic compaction gives the model no turn to prepare, so quality preparation has to be a deliberate step. Complements the Session Ledger; does not replace it. TRIGGERS: "/checkpoint", "checkpoint", "prepare compact", "prepare for compaction", "before the compact", "save the context", "compact vorbereiten", "kontext sichern", and the same intent in any other language. Fire it right before every manual /compact. Two other things can
kaposty/context-kit · ★ 1 · AI & Automation · score 74
Install: claude install-skill kaposty/context-kit
# Checkpoint: prepare for compaction, deliberately Automatic compaction is the enemy of a clean context. It fires without warning, gives the model no turn to prepare, and flattens the reasoning into a summary that keeps roughly what happened and loses why. This skill is the answer: **you turn auto off, and instead fire this checkpoint by hand whenever the window is getting full, right before you run `/compact` yourself.** The whole point is that a manual pass HAS a turn. So unlike a hook or an auto-compact, it can actually think: read the session, decide what matters, write it down well, and hand you a clean state to compact from. Quality preparation is only possible manually. This does two things a raw `/compact` cannot: it makes the durable context **complete and current** before the summary is taken, and it keeps the **red thread** (where we are, what is next) explicit on disk so nothing depends on the summary being good. ## What it is not - It does **not** run `/compact`. It prepares; you compact. The last line it prints is the go-signal, then you type `/compact`. - It is **fired by hand**, by you, before every manual `/compact`. The `Stop` hook can fire it once enough work has piled up, but that is opt-in and ships off, because a pass that starts on its own interrupts work nobody asked to interrupt. Where it is switched on, the phases are the same with one difference: an auto-fired pass is housekeeping nobody asked for, so it reports **one sentence** (it r