# ckb-reset — edge cases Reference material for the `ckb-reset` skill. Read when a run hits an unusual situation the main steps don't cover. - **Already clean** — say so and change nothing. Don't rewrite identical scaffold files to look busy. - **Run in a KB that is not a template** — this skill can't tell the difference, so if the wiki holds substantial content (say, 50+ pages or any decision records), name that in the confirmation: "This KB has 12 decision records — templates don't usually have those. Are you in the right repository?" Ask once; don't refuse if they confirm. - **`linked/` symlinks** — never follow them when deleting. `rm -rf linked/foo` where `foo` is a symlink to another KB is catastrophic and silent. Remove the *link*, never its target, and prefer leaving tier 5 alone. - **Partial failure mid-delete** — stop, report exactly what was and wasn't deleted, and point at the restore point. Don't continue on the theory that finishing is tidier. - **User asks to reset "everything including the skills"** — that's not a reset, it's deleting the KB. Say so and point at `ckb-init` for a fresh one elsewhere. - **Module installed** — module-created page types (`repository`, `component`, `spec`) are wiki content and reset with tier 1. The module itself stays installed unless tier 6 was chosen. --- *Licensed under the Apache License, Version 2.0 — see [LICENSE](../../../LICENSE) at the repository root, or .*