clear-prep

Clear Prep

Prepare the project to survive a context reset. When you are about to run /clear (or a compaction is imminent), the volatile session state — what you just did, what is half-done, what the next step is — lives only in conversation context and is lost the moment context clears. This skill persists that state into the project's durable documents, then hands you a ready-to-paste resume prompt so the next session continues seamlessly.

Two guarantees:

1. Nothing in-flight is lost — every persistent document that should reflect the current state is updated before you clear.
2. The next session starts oriented — the resume prompt tells a zero-context Claude exactly what to read, where things stand, and what to do next.

This skill writes only to documentation/state files (all git-recoverable). It does NOT commit, push, or clear context — you do that.

Input

Arguments: $ARGUMENTS

Optional:

• A short note on the intended next task (e.g., finish the CVE remediation PR) — sharpens the "next task" line in the resume prompt.
• --no-write — skip document updates; only generate the resume prompt from current state (dry-run / read-only).

Dynamic context available:

• !`git status -s 2>/dev/null || echo "(not a git repository)"` — uncommitted changes
• !`git log --oneline -8 2>/dev/null || echo "(not a git repository)"` — recent commits
• !`git branch --show-current 2>/dev/null || echo "(not a git repository)"` — active branch

Instructions

Execute the phases in order. Phase 2 is skipped when --no-write is passed.

Phase 1: Assess Session State

Reconstruct what this session actually changed and what remains open. Gather:

1. Git delta — run git status -s, git branch --show-current, and git log --oneline -8. Identify: uncommitted/untracked files, current branch, whether work has been committed or is still loose in the working tree.
2. What was done this session — from the conversation, summarize the concrete work: decisions made, files created/edited, problems solved, experiments run. Be specific (files, versions, PR numbers), not vague.
3. What is in-flight — anything half-finished: a partially written function, an unmerged PR, a plan phase mid-execution, an unanswered question, a failing test.
4. The single next action — the one most important thing the next session should do first. Prefer the argument note if the user gave one.
5. Orientation surface — detect which durable documents this project uses so the resume prompt can point at them:
   • LAB_NOTEBOOK.md (Decision Log, Open Action Items, most recent entry, Current Baseline)
   • memory/MEMORY.md and its topic files (locate the memory dir; on this repo it is <repo>/memory/ or the per-project ~/.claude/projects/.../memory/)
   • CLAUDE.md, IMPLEMENTATION_PLAN.md, CHANGELOG.md, README.md, BRIEF.md, docs/