xz1220/kempt/kempt-clean

Kempt Clean — reversible cleanup with undo

You are applying Kempt's clean plan with the user's explicit confirmation. Every change is reversible: items move to Kempt's recycle bin and the whole batch can be undone with one command. You never hard-delete anything.

Steps

1. Locate the CLI (same as kempt-checkup): command -v kempt, else

node <kempt-repo>/bin/kempt.mjs.

1. Ensure a fresh report. If the user just ran a checkup, reuse it. Otherwise run

kempt scan --json first — the clean plan is derived from the latest report.

1. Dry-run and show the plan. Run:

``bash kempt clean ``

(no --yes → dry run, nothing is touched). Summarize for the user what would be cleaned: each item's what, detail, size, and that all of it goes to the recycle bin. By default this covers safe-group items only; mention that --all would also include manual-review items such as the memory merge.

1. Ask the user to confirm. Show the item list and ask explicitly. Respect their choice;

they can also cherry-pick with --items <id,id> (ids are shown by kempt plan).

1. Apply only after a clear yes:

``bash kempt clean --yes --json ``

Report back: items cleaned, bytes reclaimed, health score before → after.

1. Always end with the undo path:

``bash kempt restore --last ``

undoes the entire batch; kempt history shows what is in the recycle bin and until when it can be restored.

Rules

• **Never run kempt clean --yes without the user's explicit confirmation in this

conversation.** A standing instruction like "clean everything from now on" from a prior session does not count.

• Never run `kempt empty-recycle` unless the user explicitly asks to permanently empty

the recycle bin — it is the only irreversible command. Warn before running it.

• Do not edit, move or delete any file under ~/.claude / ~/.codex yourself; the only

write path is the Kempt CLI, which guarantees reversibility.

• If a restore or clean fails, surface the CLI's error verbatim and stop; do not improvise

with rm/mv.