release

Ship preprod to production by creating a release PR, version tag, and GitHub Release.

Updated Aug 13, 2026
One-click install
npx skills add https://github.com/Evolutionary-Leadership/harness --skill release-evolutionary-leadership
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/Evolutionary-Leadership/harness/tree/main/.claude/setup/railway/.claude/skills/release
Command: npx skills add https://github.com/Evolutionary-Leadership/harness --skill release-evolutionary-leadership

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Shipping to production involves many error-prone manual steps: deciding the version, writing release notes, updating the changelog, tagging, and publishing a GitHub Release. This Skill automates the entire preprod-to-main release flow while forcing an explicit review of everything being shipped, so no one accidentally releases a colleague's unfinished work. ## Core Features & Use Cases - Blast-radius reporting: Before anything ships, it lists every commit and pull request queued on preprod, split into your own work versus work riding along from others. - Authority gating: A release only proceeds with an explicit grant in .harness-version or a direct user request in the current turn; flags like --ship alone are not sufficient. - Automated release mechanics: Computes the next semantic version, generates release notes and changelog entries, pushes a release commit to preprod via the GitHub MCP server, and lets the release.yml workflow merge to main, tag the version, and publish the GitHub Release. - Use Case: After merging several features into preprod during a sprint, run /release minor to review everything queued, confirm the scope, and ship a tagged v1.3.0 release to production in one command. ## Quick Start Run /release with an optional major, minor, or patch argument to review what is queued on preprod and ship it to production as a tagged GitHub Release.

Frequently Asked Questions about release

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

FAQPage Schema
How do I release preprod to production in GitHub?

Run /release with an optional version bump type (major, minor, or patch, defaulting to patch). The skill computes the next version, reports everything queued on preprod, pushes a release commit via the GitHub MCP server, and the release.yml workflow merges to main, tags the version, and creates a GitHub Release.

How do I generate release notes and a changelog automatically?

The skill categorizes commit messages into Features, Fixes, and Improvements, then builds the changelog section and release description from them. Where a changelog accumulator workflow owns the changelog, it skips composition and instead drafts a downstream release note with scripts/release-notes-brief.mjs.

Why does the release skill push via GitHub MCP instead of git push?

In the harness sandbox, the local git proxy rejects pushes to preprod or main with HTTP 403, allowing only the session's claude/ branch. The mcp__github__push_files call goes through api.github.com with the harness PAT, bypassing the proxy, and works identically outside the sandbox.

Can I release without confirming what ships?

The --quick flag skips the confirmation question but never skips the blast-radius report, which lists every commit and PR being shipped. A release still requires authority: either a grant in .harness-version or a direct user request in the current turn.

What happens if the release workflow times out or fails?

If the merge to preprod never lands or preprod never settles, the skill stops without cutting a release and tells you to re-run /release from preprod once it is quiet. If the release commit never reaches main, nothing is claimed and re-running the verification step later is the documented recovery.