ops-codegraph-tool: Skill for Claude Code

Release

You are preparing a release for @optave/codegraph.

Version argument: $ARGUMENTS

• If a version was provided (e.g. 3.1.1), use it as the target version.
• If no version was provided (empty or blank $ARGUMENTS), you will auto-detect it in Step 1b.

Important: this skill does NOT bump versions. The publish workflow (publish.yml) handles version bumping in package.json, Cargo.toml, package-lock.json, and optionalDependencies atomically — after building native binaries and publishing to npm. Bumping versions in the release PR would cause CI failures because the native prebuilt binary wouldn't exist at the new version yet.

---

Step 0: Isolate and sync

1. Create a worktree — run /worktree to get an isolated copy of the repo. All subsequent steps run inside the worktree.
2. Sync with main — fetch origin and check how far behind the current branch is:

   git fetch origin
   git rev-list --count HEAD..origin/main
   

   If the count is > 0 (behind main), detach to origin/main so all subsequent work starts from the latest main:

   git checkout origin/main
   

   Do not create the release/VERSION branch here — Step 7 creates it once VERSION is known.

Step 1a: Gather context

Run these in parallel:

1. git log --oneline v<previous-tag>..HEAD — all commits since the last release tag (use git describe --tags --match "v*" --abbrev=0 to find the previous tag)
2. Read CHANGELOG.md (first 80 lines) — understand the format
3. Read package.json — current version
4. git describe --tags --match "v*" --abbrev=0 — find the previous stable release tag

Step 1b: Determine version (if not provided)

If $ARGUMENTS is empty or blank, determine the semver bump from the commits gathered in Step 1a.

The conventional commit prefix (feat:, fix:, perf:, etc.) is a hint, not the verdict. Contributors frequently use feat(scope): for internal refactors, perf improvements, or extractor/engine accuracy fixes that don't actually add any user-facing feature. The version bump is determined by what users observe, not by the commit prefix.