upgradelisted

Migrate an existing v0.11 adr-kit project to the v0.12 footprint without re-running the heavy /adr-kit:init audit. Detects v0.11-style inline ADR Kit Rules in CLAUDE.md, replaces with the slim stub, copies templates/adr-kit-guide.md to .claude/, installs the pre-commit hook (default-on), and walks Accepted ADRs offering Enforcement-block backfill proposals one at a time. Idempotent — safe to re-run.
rvdbreemen/adr-kit · ★ 1 · AI & Automation · score 73

Install: claude install-skill rvdbreemen/adr-kit

# adr-kit upgrade You migrate a project from the v0.11 footprint to the v0.12 footprint **without** doing the heavy initial codebase audit. Use this skill when: - A project has been running adr-kit ≤ v0.11 for a while. - The ADR set is already mature (lots of Accepted ADRs). - Re-running `/adr-kit:init` would propose duplicates against existing ADRs and waste the user's time. If the project has no ADRs yet, point the user to `/adr-kit:init` instead. ## Step 1 — Detect the installed footprint Inspect the current state: - `CLAUDE.md` exists? Read it. Look for a v0.11-style `## ADR Kit Rules` section (free-form heading, no markers) OR a v0.12 `` block (markers). - `docs/adr/` exists? Count `ADR-*.md` files. Scan for any existing `## Enforcement` blocks and tally them. - `.githooks/pre-commit` exists? - `.claude/adr-kit-guide.md` exists? If yes, check the version line (first line of the plugin template is ``). Report the detected state to the user in a 4–6 line summary before changing anything. If all of the following are true, the project is already on v0.12: - CLAUDE.md has the marker-bracketed stub - `.claude/adr-kit-guide.md` matches the plugin's current version - `.githooks/pre-commit` is the adr-kit hook - All Accepted ADRs either have `## Enforcement` blocks or have been explicitly skipped If so, exit with `already on v0.12; nothing to do`. ## Step 2 — Refresh CLAUDE.md stub + guide file Resolve the plugin