Skip to main content

FOR EVERYONE

Stay updated — /kit-update

The kit keeps improving. New agents, smarter rules, better skills. /kit-update brings those improvements into your project — gently, and only when you ask.

You stay in control. Nothing changes until you've seen what's coming.

What you get​

  • A quiet nudge. When the version in your project trails the plugin you have installed, you'll see an "update available" notice. No pop-ups, no nagging — just a heads-up.
  • A changelog in plain language. It shows you what's new since your project last updated, written so anyone can read it — not a wall of technical notes.
  • A safe upgrade. It adds new files and merges new settings into your .claude/. It never overwrites the agents, skills, or rules you've shaped yourself.

The promise in one line: adds new, merges config, preserves your files.

How to run it​

In any project that was set up with /kit-init:

/kit-update

You'll see the notice, the changelog, and a preview of exactly what will be added or merged — before anything is written. If it looks good, confirm. If not, walk away; nothing has changed.

What "adds new, merges config" means​

Say a kit update introduces a new research agent and a new option in your settings.

  • The new agent file is dropped in alongside your existing ones. Your agents stay exactly as you left them.
  • The new setting is merged into your config — the new key appears, your existing values are untouched.
  • A rule you edited stays your version. The update won't clobber your wording.

Your customizations are yours. The update fills in around them.

How it works under the hood
  • Version tracking. Each project records a kitVersion in .claude/kit.config.json. /kit-update compares it against the installed plugin's version. When the project trails, the notice surfaces and the CHANGELOG delta between the two versions is rendered in plain language.
  • Merge-upgrade, not overwrite. The update runs the kit's init.sh --upgrade path. New files are written; existing files you've customized are left alone. Config files are merged key-by-key (new keys added, your values preserved) rather than replaced — jq is used for the merge where available.
  • .claudekit overrides. A per-folder .claudekit/config.json can set preferences for a whole subtree of projects. During an upgrade, the nearest folder's config wins and merges over the project config, the way .editorconfig cascades — so shared defaults apply without overriding a project's specific choices.
  • Always previews first. No write happens until you confirm the previewed plan.