release

Automate GitHub repository releases with version bumping, PR creation, and tag pushing.

Updated Jul 6, 2026
One-click install
npx skills add https://github.com/zhaow-de/zcrypto-kraken --skill release-zhaow-de
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/zhaow-de/zcrypto-kraken/tree/main/.claude/skills/release
Command: npx skills add https://github.com/zhaow-de/zcrypto-kraken --skill release-zhaow-de

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, gh, python3, uv, commitizen, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the release process for GitHub repositories, including version bumping, PR creation, tag pushing, and GitHub Release creation.

Core Features & Use Cases

  • Version Bumping: Automatically updates version numbers in pyproject.toml, README, and creates a new tag.
  • PR Creation: Creates a pull request from develop to main with a release note.
  • Tag Pushing: Pushes the new tag to the main branch.
  • GitHub Release: Creates a GitHub Release with the new version's changelog section as the description.
  • Back-Merge: Back-merges main into develop to keep branches in sync.
  • Use Case: Ideal for teams that need to streamline their release process and ensure consistency across branches.

Quick Start

Run the release skill to automate the release process for your GitHub repository.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate GitHub release management and version bumping?

GitHub release management is automated by bumping versions in pyproject.toml, creating a develop-to-main pull request, pushing tags, and generating GitHub Releases with changelog descriptions.

What is the best way to streamline GitHub release processes for continuous integration?

Streamlining GitHub release processes involves automating version control updates, tag pushing, and back-merging main into develop to keep branches synchronized across your software development workflow.

Do I need commitizen and gh to automate repository versioning and release creation?

Yes, automating repository versioning and GitHub Release creation requires git, gh, python3, uv, and commitizen to manage the release process and generate changelog sections.

How does version control automation handle back-merging branches during a release?

Version control automation handles back-merging by pushing the new tag to the main branch and then back-merging main into develop to ensure both branches remain in sync.

Can I automatically create a GitHub Release with a changelog from pyproject.toml?

Yes, a GitHub Release is automatically created using the new version's changelog section as the description after updating the version number in pyproject.toml and README.

Why does release automation create a pull request before pushing a new tag?

Release automation creates a pull request from develop to main with a release note before pushing the tag to ensure code review and maintain consistency across branches.