release

Analyze Conventional Commits to draft changelogs and create release commits and tags.

2|Updated Apr 10, 2026
One-click install
npx skills add https://github.com/t0lab/harness-kit --skill release-t0lab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/t0lab/harness-kit/tree/main/.agents/skills/release
Command: npx skills add https://github.com/t0lab/harness-kit --skill release-t0lab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create reliable, auditable releases from a repository's current branch state without guessing the correct version, losing changelog history, or accidentally publishing unverified changes. The workflow reduces human error by analyzing commits, recommending semver bumps, drafting changelogs, and staging only release artifacts for commit and tag.

Core Features & Use Cases

  • Analyze commit history (excluding merge and bot noise) and detect BREAKING CHANGE signals.
  • Recommend SemVer bumps with explicit rationale and show current -> proposed version.
  • Draft Keep-a-Changelog style entries rewritten for end users and prepend them to CHANGELOG.md.
  • Run verification gates (tests, lint/typecheck/build) and require fresh evidence before releasing.
  • Create release commit and annotated tag, optionally push refs and create a GitHub release after explicit confirmation.
  • Use case: prepare a stable patch, minor, or major release from main or a release branch while preserving changelog integrity and auditability.

Quick Start

Run a dry-run release analysis, review the proposed version bump and changelog preview, then confirm to create the release commit and tag.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate a Git release workflow from Conventional Commits?

Automate a Git release by analyzing Conventional Commits to classify changes, recommend a SemVer version bump, draft a changelog, and stage a release commit with an annotated tag. The workflow requires explicit confirmation before pushing refs or publishing.

How does SemVer version bumping work with commit history analysis?

SemVer version bumping analyzes commit history to detect BREAKING CHANGE signals and standard commit types, excluding merge and bot noise. It then recommends a patch, minor, or major version bump with explicit rationale, comparing the current version to the proposed release version.

Can I generate a Keep-a-Changelog style changelog automatically from Git commits?

Yes, you can generate a Keep-a-Changelog style changelog automatically. The workflow drafts changelog entries by classifying Git commits and rewriting them for end users, then prepends the new entries directly to your existing CHANGELOG.md file to preserve history.

Do I need to run tests and build checks before creating a release tag?

Yes, running verification gates like tests, lint, typecheck, and build checks is required before creating a release tag. The workflow requires fresh evidence from these gates passing successfully to ensure unverified changes are not accidentally released.

What is the safest way to prepare a version release without accidentally publishing unverified changes?

The safest way to prepare a version release is using a dry-run analysis to review the proposed version bump and changelog preview. This stages only release artifacts for commit and tag creation, requiring your explicit confirmation before any push or publish action occurs.

How do I exclude merge commits and bot noise from my changelog generation?

Exclude merge commits and bot noise from changelog generation by using commit history analysis that automatically filters out this noise. The workflow classifies only meaningful Conventional Commits to draft accurate Keep-a-Changelog entries and recommend appropriate SemVer bumps.