release-jetbrains

Automates the Kilo JetBrains plugin release workflow from version resolution through Marketplace publish.

27.1k|3.1k|Updated Mar 10, 2025
One-click install
npx skills add https://github.com/Kilo-Org/kilocode --skill release-jetbrains
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-jetbrains
Source: https://github.com/Kilo-Org/kilocode/tree/main/.kilo/skills/release-jetbrains
Command: npx skills add https://github.com/Kilo-Org/kilocode --skill release-jetbrains

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires semver, and includes scripts (resource) components.

What problem does it solve?

Releasing the Kilo JetBrains plugin involves many error-prone manual steps: resolving the next RC or stable version, verifying the pinned CLI version, dispatching GitHub Actions workflows, editing changelogs, and watching publish runs. This Skill orchestrates the entire release pipeline with safety checks so maintainers avoid tagging mistakes and incomplete releases.

Core Features & Use Cases

  • Version Resolution: Computes the next RC or stable version from existing jetbrains/v* git tags, or accepts an explicit semver.
  • CLI Pin Verification: Checks that the JetBrains plugin's pinned Kilo CLI version on origin/main matches the intended release and that all runtime assets exist, with drift detection and a pin-bump PR workflow.
  • Release Orchestration: Dispatches the prepare workflow, drafts a filtered human-readable changelog from the release range, commits it to the release branch via the GitHub contents API, and watches the publish workflow to completion.
  • Use Case: A maintainer asks to release the next JetBrains RC; the Skill resolves 7.0.1-rc.7, confirms the CLI pin is up to date, dispatches prepare, helps edit the changelog, and reports the Marketplace channel and GitHub Release URL after merge.

Quick Start

Ask the agent to release the next RC of the Kilo JetBrains plugin and confirm the resolved version when prompted.

Frequently Asked Questions about release-jetbrains

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I release the Kilo JetBrains plugin?

Run the release skill from the repository root: resolve a version with resolve-version.ts, verify the CLI pin with check-pin.ts, dispatch the prepare workflow, edit and commit the changelog, then merge the release PR and watch the publish workflow to completion.

How do I resolve the next RC or stable version for a JetBrains release?

Run resolve-version.ts with --spec "next rc" or "next stable". It inspects existing jetbrains/v* git tags: next rc increments the rc number or starts rc.1 on the next patch, while next stable uses the RC base version or the next patch.

What GitHub permissions are needed to dispatch release workflows?

The gh CLI must be authenticated for Kilo-Org/kilocode with repo and workflow scopes, refreshable via gh auth refresh -s repo -s workflow. Fine-grained tokens need Actions, Contents, and Pull requests read/write; merging requires collaborator permission.

Why does the CLI pin check report drift before a release?

Drift means the pinned CLI on origin/main is behind the latest CLI release, the worktree differs from main, repo dev mode is enabled, or runtime assets are missing. Resolve the drift by bumping the pin via a PR to main before dispatching prepare.

Can the skill move or delete JetBrains release tags?

No. The skill must never move, delete, or recreate jetbrains/v* tags because the prepare workflow creates immutable tags. If a tag points to an unexpected commit, stop and inspect manually instead of retagging.

What happens if the publish workflow fails after merging the release PR?

Rerun the failed workflow only if the Marketplace did not already accept the version. If Marketplace succeeded but the GitHub Release upload failed, manually create or edit the GitHub Release for jetbrains/v<version> using the reviewed changelog.