harness-release

Name: harness-release
Availability: InStock
Author: fockus

Automate Harness v3 release workflows with version bumps, changelog updates, and GitHub Releases.

2|Updated Mar 30, 2026

Search Tags:#automation #changelog #release #semver #version-bump #github-release

Ready to run

npx skills add https://github.com/fockus/claude-skill-build --skill harness-release-fockus

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: harness-release
Source: https://github.com/fockus/claude-skill-build/tree/main/skills/harness-release
Command: npx skills add https://github.com/fockus/claude-skill-build --skill harness-release-fockus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Harness v3 release automation consolidates and streamlines the entire release process, including changelog updates, version bumps, tag creation, and GitHub Release publishing, removing manual, error-prone steps.

Core Features & Use Cases

Unified release automation: orchestrates version bumps, changelog updates, tag creation, and GitHub Release generation from a single workflow.
Pre-flight checks & governance: enforces branch policies, ensures clean working trees, and validates prerequisites before releasing.
Flexible launch modes: supports interactive and autonomous release flows for patch, minor, and major versions across single or multi-repo setups.
Use Case: when preparing a production release, trigger /release to compute the next version, update CHANGELOG.md, create a tag, and publish a GitHub Release, with optional announcements.

Quick Start

Trigger the release workflow with /release and follow prompts to choose patch, minor, or major.

Frequently Asked Questions about harness-release

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

FAQPage Schema

How do I automate a GitHub Release with semantic versioning and changelog updates?▼

You can automate a GitHub Release with semantic versioning by triggering a release workflow that calculates version bumps, synchronizes CHANGELOG.md, creates tags, and publishes the release. This process enforces semver rules and updates VERSION files automatically.

What's the best way to manage multi-repo release workflows for production deployments?▼

Managing multi-repo release workflows is handled by automating version bump calculations and changelog synchronization across repositories. The workflow enforces pre-flight checks like branch policies and clean working trees before proceeding with tag creation and publication.

How do pre-flight checks work for version bump automation?▼

Pre-flight checks for version bump automation enforce branch policies and ensure a clean working tree before releasing. These governance checks validate prerequisites to prevent errors during semantic version calculation and GitHub Release publication.

Can I choose between patch, minor, and major version bumps interactively?▼

Yes, you can choose between patch, minor, and major version bumps interactively. The release workflow supports flexible launch modes, allowing you to select the semantic version increment and follow prompts to complete the changelog and tag updates.

Does automated release management support both single-repo and multi-repo setups?▼

Automated release management supports both single-repo and multi-repo setups. It orchestrates version bumps, changelog updates, tag creation, and GitHub Release generation across different repository configurations while enforcing semantic versioning.

Why do I need a clean working tree before publishing a GitHub Release?▼

A clean working tree is required before publishing a GitHub Release to prevent uncommitted changes from interfering with version bumps and changelog synchronization. Pre-flight checks enforce this state to ensure release integrity across single and multi-repo workflows.