repack
/repack
Refresh a long chat — write the next-session handoff, then hand the user /clear → /continue so the work resumes in a fresh context window. Use when the context nudge reaches the handoff level, or the user says "repack", "refresh the chat", "context is getting full", "fresh session", "start clean". If the topic is already done, skip the handoff and just offer /clear.
- Author
- optimiziramsi ↗
- Repository
- skills ↗
- Licence
- MIT
- Last repository change
- 27.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Refresh a long chat — write the next-session handoff, then hand the user /clear → /continue so the work resumes in a fresh context window. Use when the context nudge reaches the handoff level, or the user says "repack", "refresh the chat", "context is getting full", "fresh session", "start clean". If the topic is already done, skip the handoff and just offer /clear.
Triggers from the description
Original author description
Refresh a long chat — write the next-session handoff, then hand the user /clear → /continue so the work resumes in a fresh context window. Use when the context nudge reaches the handoff level, or the user says "repack", "refresh the chat", "context is getting full", "fresh session", "start clean". If the topic is already done, skip the handoff and just offer /clear.
How it works
- Steps
- Rules
SKILL.md preview
--- name: repack description: >- Refresh a long chat — write the next-session handoff, then hand the user /clear → /continue so the work resumes in a fresh context window. Use when the context nudge reaches the handoff level, or the user says "repack", "refresh the chat", "context is getting full", "fresh session", "start clean". If the topic is already done, skip the handoff and just offer /clear. --- # repack — fresh context, same work A long session degrades: early context gets compressed or lost, and every turn costs more. Repack moves what matters into a handoff file, so a fresh session picks the work up with none of the weight. The agent cannot clear or compact a session — that is always the user's `/clear` (or `/compact`). ## Steps 1. **Topic already done?** If the user says so (or the work is landed and nothing is pending), skip the handoff: say in one line that the topic is closed and `/clear` is safe. Stop. 2. **Close what's open.** Uncommitted work: commit it per the project's commit rules (the `commit` skill where enabled), or name it in the handoff as uncommitted — never leave it unmentioned. 3. **Write the handoff.** Use the `handoff` skill when it is enabled (the `session` plugin) — it owns the format and the 4k cap. Otherwise write `.agent/handoff.md` yourself: current state (branch, last commit, what is done), decisions a cold session can't re-derive, the exact next step, and open questions. Facts, not narrative; no secrets or personal data. 4. **Hand over.** Tell the user, in two lines: the handoff is written (path), then run `/clear` and say `continue` (or `/continue` where the `session` plugin is enabled) in the fresh session. Offer `/compact` instead only if they'd rather keep this thread. ## Rules - Don't start new work after the handoff is written — the next step belongs to the fresh session. - The handoff is for the next session, not a report: no recap of this conversation's process.
Versions
The database has no other skills named repack.
Database snapshot: 13.11.2026 · package version 02f16446a7f2 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100th-clear
Hand this session off and continue in a fresh context in the SAME terminal — the th-handoff checkpoint, then `th harness handoff arm`, then the user types `/clear` and `/th-handoff resume <pearl>` (the armed token usually resumes on its own). Invoke as `/th-clear [pearl-id]`.… - 86handoff
Write or update a HANDOFF.md so a fresh agent can continue this work. Use when the user says "handoff", "compact this", "context is full", or "/clear and continue". - 100writing-handoffs
Use when the user asks for a handoff prompt, a continuation prompt, or a prompt to continue work in a fresh context window — often phrased as 'give me a handoff prompt', 'I'll clear context', 'so I can continue in a new session'. Also use when wrapping up a session on a… - 90handoff
Write a handoff document so another agent or a fresh session can continue this work. Use for "handoff", "hand this off", "write a handoff", "continue this in a new session" or "pass this to another agent". For deciding whether to compact or clear, use session-budget. - 100session-handoff
Write or update handoff.md so the next agent, starting with a fresh context, can continue this work - the goal, the progress, what worked, what did not, and the next steps. The file stays out of git. Use when the user wants to hand the work over, end the session, or continue in a clean context. - 100session-handoff
Use when a work session is ending, or the context window is getting full, and someone (you or a fresh session) must continue later. Writes a short HANDOFF.md that can be checked against the real files.