release

Automate versioning, changelog generation, and release deployment via PR-based workflows.

1|Updated Feb 28, 2026
One-click install
npx skills add https://github.com/im9/inboil --skill release-im9
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/im9/inboil/tree/main/.claude/skills/release
Command: npx skills add https://github.com/im9/inboil --skill release-im9

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bump software versions, generate changelog drafts, and publish releases using a safe PR-based workflow.

Core Features & Use Cases

  • Version bumping: automatically compute patch/minor/major updates from commits and tags.
  • Changelog drafting: generate Keep a Changelog-compliant notes for the upcoming release.
  • Release orchestration: create PRs, tag the release, and deploy to GitHub Releases after merge.
  • Use Case: Prepare a new product update by running the release command to create an auditable, reviewable release process.

Quick Start

Run the release command with an optional bump type to start the release workflow.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate versioning and changelog generation for a GitHub release?

You can automate versioning and changelog generation by running an automated release workflow that computes version bumps from commits, drafts Keep a Changelog-compliant notes, and deploys to GitHub Releases. It safely orchestrates tagging and release deployment through a PR-based workflow.

How do I calculate the next semantic version bump from Git commits?

To calculate the next semantic version bump from Git commits, the release automation analyzes your commit history and existing tags to automatically determine whether a patch, minor, or major version update is required for your software project.

Can I use a PR-based workflow to safely publish GitHub releases?

Yes, you can use a PR-based workflow to safely publish GitHub releases. The process creates a pull request for the version bump and changelog, requiring user confirmation and validation before merging to tag and deploy the release.

How do I generate a Keep a Changelog-compliant draft for an upcoming release?

To generate a Keep a Changelog-compliant draft for an upcoming release, the release workflow automatically parses recent commits to construct formatted release notes, which are then submitted for review within a pull request.

What are the limitations of automating releases on a main-branch workflow?

Automating releases on a main-branch workflow requires pre-flight checks and applies specifically to PR-based releases. It is limited to main-branch release workflows and requires user confirmation steps before final tagging and deployment to GitHub Releases.