release-jetbrains

name	release-jetbrains
description	Use when releasing the Kilo JetBrains plugin -- resolve a version ("next rc" or explicit), run the prepare workflow, edit and commit a filtered human-readable changelog on the release PR, then watch publish to completion.

JetBrains Release

Use this skill when releasing the Kilo JetBrains plugin.

This skill drives the existing JetBrains release workflows. It must not move, delete, or recreate JetBrains release tags. It must always confirm the resolved version with the user before dispatching the prepare workflow because the prepare workflow creates an immutable jetbrains/v<version> tag.

Preconditions

• Run from the repository root.
• gh must be authenticated for Kilo-Org/kilocode with permission to dispatch workflows, read PRs, and write contents. Merge permission is only required if the user asks the skill to merge the release PR automatically.
• Check auth with gh auth status. For GitHub CLI OAuth, refresh common release scopes with gh auth refresh -s repo -s workflow; repo covers private-repo contents and PR operations, and workflow allows workflow dispatch. If using a fine-grained token instead, grant repository permissions for Actions read/write, Contents read/write, and Pull requests read/write. Merging still requires normal repository collaborator permission or a token/user allowed by branch protection.
• Reference packages/kilo-jetbrains/RELEASING.md for manual recovery rules.
• Do not locally check out the generated release branch. The helper scripts update the release branch through GitHub to avoid disturbing the current worktree.

Version Resolution

Resolve the user's version request:

bun .kilo/skills/release-jetbrains/script/resolve-version.ts --spec "next rc"

Accepted specs:

Spec	Meaning
next rc	If the latest JetBrains tag is an RC, increment its rc.n; otherwise start the next patch RC at rc.1.
next stable	If the latest JetBrains tag is an RC, use its base version; otherwise use the next patch stable.
x.y.z-rc.n	Explicit RC release.
x.y.z	Explicit stable release.

Show the resolved version, kind, and default fromTagDefault to the user and ask for confirmation before continuing.

Prepare Workflow

After confirmation, dispatch and watch the prepare workflow:

bun .kilo/skills/release-jetbrains/script/dispatch-prepare.ts --kind rc --version 7.0.1-rc.7

Pass a generous Bash timeout, such as 1800000 ms, because the script blocks on gh run watch --exit-status. If the shell times out but the workflow is still running, re-attach with:

bun .kilo/skills/release-jetbrains/script/dispatch-prepare.ts --kind rc --version 7.0.1-rc.7 --run-id <run-id>

The script prints prNumber, prUrl, runUrl, and branch on success.

Changelog Draft

Create a changelog draft after the prepare PR exists:

1. Read the PR body with gh pr view <pr> --json body.
2. Extract JetBrains-From-Tag, JetBrains-Tag, and ## Generated Notes.
3. Use the release range and path filter as the primary relevance signal:

git log --oneline <from-tag>..<tag> -- packages/opencode packages/kilo-jetbrains

Keep JetBrains and CLI/runtime changes. Drop unrelated VS Code, docs, gateway, telemetry, i18n, desktop, and webview-only changes unless they affect the CLI bundled into the JetBrains plugin.

Rewrite terse commit or PR titles into user-facing bullets grouped under ### Added, ### Fixed, and ### Changed. Keep the exact generated header format:

## [<version>] - <date>

Write the editable draft to:

packages/kilo-jetbrains/build/release/<version>-changelog.md

Include source context in an HTML comment so it is easy to edit but not shipped:

<!-- CONTEXT - deleted automatically on commit. Source PRs in range:
- #1234 feat(jetbrains): ... https://github.com/Kilo-Org/kilocode/pull/1234
- #1235 fix(cli): ... https://github.com/Kilo-Org/kilocode/pull/1235
-->

Ask the user to edit the file and confirm when done.

Commit Changelog

After the user confirms the draft is ready, strip the <!-- CONTEXT ... --> block into a temporary cleaned file, then commit the cleaned section to the release branch:

bun .kilo/skills/release-jetbrains/script/update-changelog.ts --version 7.0.1-rc.7 --file /path/to/clean-section.md

The script updates packages/kilo-jetbrains/CHANGELOG.md on jetbrains/release/v<version> through the GitHub contents API and commits with:

docs(jetbrains): edit changelog for v<version>

Approve And Publish

Ask the user to approve the release changelog and metadata. By default, have the user merge the release PR manually in GitHub, then watch the publish workflow:

bun .kilo/skills/release-jetbrains/script/watch-publish.ts --pr <number> --version 7.0.1-rc.7

Only merge automatically when the user explicitly asks for it and gh has merge permission:

bun .kilo/skills/release-jetbrains/script/watch-publish.ts --pr <number> --version 7.0.1-rc.7 --merge

Pass a generous Bash timeout, such as 1800000 ms. If the shell times out, re-attach with:

bun .kilo/skills/release-jetbrains/script/watch-publish.ts --pr <number> --version 7.0.1-rc.7 --run-id <run-id>

Report the Marketplace channel and GitHub Release URL. RC versions publish to the eap channel; stable versions publish to the default Marketplace channel.

Recovery

• If prepare created the tag but failed before creating a PR, rerun prepare for the same version. The existing workflow reuses the tag if it points to the same commit.
• If a tag points to an unexpected SHA, stop and inspect manually. Do not move or delete release tags casually.
• If publish fails after merge, rerun the failed workflow only if Marketplace did not already accept the version.
• If Marketplace succeeds but GitHub Release upload fails, manually create or edit the GitHub Release for jetbrains/v<version> using the reviewed changelog.