release

Automate versioned releases by bumping versions, tagging commits, and generating GitHub releases.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates versioned releases by bumping versions, tagging merged commits, creating GitHub releases, and triggering CI to publish to npm. This eliminates manual steps and ensures release traceability.

Core Features & Use Cases

  • Bump version via PR and tag the merge commit
  • Create GitHub release notes and publish through CI
  • Support prerelease workflows and safe rollback procedures

Quick Start

Initiate a version release by creating a PR to bump the version and trigger CI to publish.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate versioned releases and git tagging in a CI pipeline?

Automate versioned releases by bumping versions via PRs, tagging merged commits, and generating GitHub releases to trigger CI pipelines for npm publishing. This eliminates manual steps and ensures release traceability.

What's the best way to trigger an npm publish through GitHub releases?

Trigger an npm publish by creating a PR to bump the version, which tags the merge commit and creates a GitHub release, allowing CI to publish to npm after successful checks.

Can I create prerelease workflows and perform safe rollbacks with git tagging?

Yes, you can create prerelease workflows and perform safe rollback procedures using standard git tagging and GitHub release features within your CI pipelines.

Do I need a repository with PR-based version bumps to automate GitHub releases?

Yes, automating versioned release management requires a repository with PR-based version bumps, CI that publishes after successful checks, and npm access to function correctly.

Why does my CI pipeline fail to publish to npm after a git tag?

CI pipelines fail to publish to npm when the repository lacks PR-based version bumps, proper npm access, or CI configurations that publish only after successful checks.