Add skills for updating the project version number

.cursor/skills/release/SKILL.md

@@ -0,0 +1,17 @@
+---
+name: release
+description: >-
+  Bump the project version across all release branches and commit the changes.
+  Use when the user asks to do a release or update the version on all branches.
+---
+
+# Release
+
+For each branch in [release-branches.md](release-branches.md):
+
+1. `git checkout <branch>`
+2. `git checkout -b version-bump-<new-version>-<branch>`
+3. Apply the [update-version](../update-version/SKILL.md) skill
+4. Commit: `Bump version from <old-version> to <new-version>`
+
+Return to the starting branch when done. Do not push.

.cursor/skills/release/release-branches.md

@@ -0,0 +1,2 @@
+- main
+- pattern-fly-5

.cursor/skills/update-version/SKILL.md

@@ -0,0 +1,31 @@
+---
+name: update-version
+description: >-
+  Update the project version number across all files that contain it on the
+  current branch. Use when bumping the version on a single branch only. For a
+  full multi-branch release, use the release skill instead.
+---
+
+# Update Version
+
+## Steps
+
+1. **Determine the new version.** If the user didn't specify one, read the
+   current version from `package.json` and bump the patch version number.
+
+2. **Update `package.json`** — replace the version string in both the top-level
+   `version` field and the `consolePlugin.version` field. Both must match.
+
+3. **Update `src/components/OverviewDetail.tsx`** — replace the old version
+   string in the JSX with the new one.
+
+4. **Sync the lockfile** — run `npm install` to propagate the version change
+   into `package-lock.json`.
+
+5. **Verify** — search the workspace for the old version string to confirm no
+   stale references remain (ignore `node_modules/` and `dist/`). Report any
+   unexpected occurrences to the user.
+
+## Version format
+
+This project uses semver (`MAJOR.MINOR.PATCH`)