keel-update

# /keel-update — sync this project with the latest Keel template Use when the kit was **cloned** a while ago and the template has since improved (hardened hooks, doc fixes, workflow updates). Pull model: run it IN the project, review diffs, approve. Non-destructive is the hard rule (same spirit as `/keel-adopt`): nothing is applied without a shown diff + an explicit yes. **Plugin half first:** if the `keel` plugin is installed (skills show up as `/keel:keel-*`), the *live* tooling (skills · agents · hooks) updates centrally — run `/plugin marketplace update keel` for that half. The buckets below still apply in full: a plugin never writes repo files, so the committed `.claude/**` copies (what standalone / no-plugin sessions run), `.claude-plugin/**`, and the template docs are synced here. ## 1. Fetch the latest template (never inside the project) ```bash rm -rf /tmp/keel-latest # idempotent — clear the stale clone a previous /keel-update run left behind git clone --depth 1 https://github.com/muratsilahtaroglu/claude-code-starter-kit /tmp/keel-latest git -C /tmp/keel-latest rev-parse --short HEAD # record for the handover line ``` ## 2. Classify every template path into three buckets - **PROTECTED — never touched (project-owned):** `HANDOVER.md` · `LESSONS.md` · `TASKS.md` · `PLAN.md` · `docs/handover-archive.md` · `docs/architecture.md` · `docs/adr/*` (except the kit-owned `0000` template and the folder `README.md` — those are TOOLING) · `CLAUDE.md` · `README.md` ·...