cani-clisted
Install: claude install-skill Yang-woo/cani-c
# cani-c
The user is about to run `/compact` or `/clear`. Three jobs:
1. Decide which one is right. One line.
2. Write a handoff so the next session can continue without loss.
3. Give the exact command to type, as the last line.
The full transcript already lives in `~/.claude/projects/<project>/<sessionId>.jsonl`. The handoff is not a summary; it is only what resuming needs. Details can be recovered later with `/resume <sessionId>` or by grepping the jsonl.
## Arguments
| Argument | Meaning |
|---|---|
| (none) | Judgment mode. I pick compact or clear. |
| `clear` / `compact` | Skip judgment, proceed with the given one. |
| `memory` / `file` | Where to store the handoff. If omitted, use the saved preference. If none is saved, ask once and store the answer as a `user` memory named `cani-c-target` so it is never asked again. |
| `done` | The previous handoff has been worked through. Delete the memory file and its MEMORY.md index line, or delete the file. |
## Judgment (no argument)
- **compact**: the remaining work depends heavily on details currently in context (open file contents, an in-progress diff, an error log just seen). Work was interrupted mid-task.
- **clear**: a unit of work is finished and the next task can start fresh. Or the context already holds a lot of stale information that would pollute a compact summary.
- When in doubt, clear. With a handoff in place, clear is cleaner. Compact is lossy compression and you cannot tell what was dropped.
When recommendi