kaposty
UserA long session makes Claude Code dumber: compaction keeps what happened and throws away why, so it retries the path you already dropped. This kit keeps a session ledger, the one file where each decision keeps its reason and its proof, and brings project state and memory current with it before every /compact. /brief shows you where things stand.
Categories
Indexed Skills (4)
brief
Briefing on what happened while you were away, so a person can stay in the loop over autonomous work. Answers "what happened", which no built in display does: /status shows active settings sources, /permissions the resolved rules, /context what is loaded. Reads the transcript, git and the hook log for facts, the session ledger and project state file for the reasons, then writes six short blocks: progress, in progress, blocked, learned, open problems, next steps. Reports only, never acts, and writes no file. TRIGGERS: "/brief", "brief me", "what happened", "where do we stand", "catch me up", "was ist passiert", "wo stehen wir", and the same intent in any other language. Project agnostic: no assumptions about language, stack, or repository layout.
checkpoint
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
session-ledger
Keep a session's durable reasoning alive across context compaction. Maintains a small on-disk ledger of what was decided, what is still open, what was verified and by which command, and what was dropped and why. A compaction summary flattens reasoning; this preserves it. Invoke explicitly to start, inspect, repair, or hand over a ledger. The per-session maintenance discipline is primed automatically by the session-start hook, so routine appends need no invocation. Project-agnostic: no assumptions about language, stack, or repository layout.
saop
Plan a non-trivial task with the SAOP method before starting the work: Sketch, Analyze, Optimize, Partition. It first locks the goal with you, grounds itself in the real context, then returns a decomposed plan pyramid whose endpoints are each checkable, ready for approval, and never implements a planned task until you approve. Domain-agnostic: a new project or subproject, a feature, a migration, a security hardening, a compliance review, a backend. Invoke it explicitly with /saop; it does not fire on its own. Skips routine or well-understood tasks where a full four-phase pass would be overkill.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.