release

Merge PRs, tag versions, and publish GitHub releases with changelog notes.

25|2|Updated Oct 20, 2025
One-click install
npx skills add https://github.com/corv89/shannot --skill release-corv89
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/corv89/shannot/tree/main/.claude/skills/release
Command: npx skills add https://github.com/corv89/shannot --skill release-corv89

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the end-to-end release workflow for software projects: merging PRs, tagging version numbers, and publishing GitHub releases with changelog notes, reducing manual toil and ensuring release traceability.

Core Features & Use Cases

  • End-to-end release automation: merge PRs, tag versions, and publish GitHub releases with automatically extracted changelog notes.
  • Version discipline: verify PR status, ensure version in pyproject.toml matches intended release, and push deterministic tags.
  • Safe rollback: guidance for undoing actions if a release fails, including removing tags and reopening PRs when necessary.

Quick Start

Execute the release workflow to automatically merge the PR, tag the version, and publish a GitHub release with changelog notes.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate GitHub PR releases and generate changelogs?

Automating GitHub PR releases involves merging pull requests, tagging version numbers, and publishing GitHub releases with automatically extracted changelog notes to reduce manual toil.

What steps are required to publish a GitHub release from a PR?

Publishing a GitHub release requires verifying CI checks, validating the version in pyproject.toml, merging the PR, pushing a deterministic git tag, and extracting release notes using gh CLI.

Do I need to update pyproject.toml before running the release workflow?

Yes, you must update the version in pyproject.toml to match your intended release. The workflow verifies this version number before proceeding with the PR merge and tagging process.

Can I undo a GitHub release if the automated workflow fails?

Yes, the workflow provides safe rollback guidance for failed releases, including instructions for removing pushed git tags, deleting the GitHub release, and reopening the merged PR when necessary.

What are the limitations of using gh CLI for end-to-end release automation?

This release automation is limited to software projects using GitHub PR processes, requiring an existing PR, passing CI checks, local git access, and the gh CLI to execute merge and publish commands.