release

Automate version updates, changelog generation, and release pull requests from develop to main.

4|Updated Jul 13, 2025
One-click install
npx skills add https://github.com/akiojin/gwt --skill release-akiojin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/akiojin/gwt/tree/main/.codex/skills/release
Command: npx skills add https://github.com/akiojin/gwt --skill release-akiojin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of updating versions, generating changelogs, and creating release pull requests, streamlining your software release workflow.

Core Features & Use Cases

  • Automated Versioning: Updates version numbers in relevant project files.
  • Changelog Generation: Automatically updates the CHANGELOG.md file.
  • Release PR Creation: Creates a pull request from the develop branch to the main branch for release.
  • Use Case: When you're ready to ship a new version of your software, use this Skill to handle the repetitive tasks of version bumping, changelog updates, and PR creation, allowing you to focus on the code.

Quick Start

Use the release skill to prepare and create a new release.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate version releases and changelog updates for GitHub Actions?

You can automate version releases and changelog updates by using tools like git-cliff and gh CLI to generate commits, modify CHANGELOG.md, and create a release pull request from the develop branch to the main branch.

What is the best way to create a release pull request from develop to main?

Creating a release pull request from develop to main is best handled by automating branch checks, remote synchronization, commit generation, and version updating within your CI/CD pipeline before opening the PR.

Can I use git-cliff with GitHub Actions to generate a changelog?

Yes, git-cliff can be integrated with GitHub Actions to automatically generate and modify your CHANGELOG.md file as part of an automated versioning and release pull request workflow.

Does automated versioning require syncing remote branches before creating a release PR?

Automated versioning requires remote synchronization to ensure project readiness for a new release, verifying that your local develop branch is up to date before generating commits and creating a pull request to main.

Why does my release workflow need to perform branch checks before bumping versions?

Release workflows need branch checks to ensure you are operating from the correct develop branch, preventing version conflicts and ensuring the generated changelog and release pull request target the correct main branch.

Are there limitations to using gh CLI for release PR automation?

Using gh CLI for release PR automation is limited to Git-based versioning and changelog management workflows, requiring a properly configured GitHub repository with distinct develop and main branches to function correctly.