release

Automate version bumps, PR creation, tag publishing, and GitHub releases.

1|2|Updated Jan 16, 2026
One-click install
npx skills add https://github.com/kynetic-ai/kynetic-spec --skill release-kynetic-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/kynetic-ai/kynetic-spec/tree/main/.claude/skills/release
Command: npx skills add https://github.com/kynetic-ai/kynetic-spec --skill release-kynetic-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Replaces manual release processes by automating version bumps, PR creation, tag publishing, and GitHub release generation to streamline software delivery.

Core Features & Use Cases

  • Bump version via PR and keep package.json in sync with tags
  • Create a Git tag on the merged commit and generate a GitHub release
  • Leverage CI to publish to npm and ensure reproducible releases
  • Supports dry-run previews and prerelease options for alpha/beta/rc workflows

Quick Start

Trigger a release by running the /release command with optional modifiers (patch, minor, major, or a specific version) to begin the end-to-end workflow.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate a GitHub release and npm publish from a PR merge?

This Skill automates npm publish and GitHub release generation by bumping versions via PR, creating Git tags on merged commits, and leveraging CI to publish. It aggregates release notes from commits to streamline software delivery.

What is a PR-driven release workflow for package versioning?

A PR-driven release workflow manages version bumps via pull requests, enforcing a clean working tree and up-to-date origin. Upon merge, it automatically creates unique Git tags and publishes packages, replacing manual release processes.

Can I preview a version bump and release before merging?

Yes, you can preview a version bump and release before merging using the dry-run option. This validates aggregated release notes and proposed version changes without publishing a tag to GitHub or npm.

Does this release automation support prerelease versions like alpha and beta?

Yes, this release automation supports prerelease versions like alpha, beta, and rc. You can trigger these specific prerelease workflows using optional modifiers when running the release command.

What constraints are enforced when automating Git tags and version bumps?

When automating Git tags and version bumps, the workflow enforces a clean working tree, an up-to-date origin, and unique tags. These constraints prevent conflicting releases and ensure reproducible software delivery.

How do I aggregate commit messages into release notes?

To aggregate commit messages into release notes, the release workflow automatically parses commit history between tags. It compiles these commits to generate the GitHub release description, eliminating manual note writing.