release-pr

Create release pull requests and tags by analyzing conventional commit messages.

1|1|Updated Feb 1, 2026
One-click install
npx skills add https://github.com/corbat-tech/coco --skill release-pr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-pr
Source: https://github.com/corbat-tech/coco/tree/main/.claude/skills/release-pr
Command: npx skills add https://github.com/corbat-tech/coco --skill release-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires node, git, gh, and includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the process of creating software releases by automating version bumping, tagging, and merging, reducing manual errors and saving development time.

Core Features & Use Cases

  • Automated Version Bumping: Intelligently determines whether a patch, minor, or major version bump is needed based on commit messages (Conventional Commits).
  • Tagging and Merging: Creates a Git tag for the new version and merges the feature branch into the main branch.
  • Use Case: After merging a set of features into a merge/* branch, run this Skill to prepare and push a new release to your main branch and remote repository.

Quick Start

Run the release-pr skill to create a patch release from the current merge branch.

Frequently Asked Questions about release-pr

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

FAQPage Schema
How do I automate version bumping and release pull requests using conventional commits?

Automate version bumping by analyzing conventional commit history to determine patch, minor, or major increments, then generate a release pull request. This process requires Git, Node.js, and the GitHub CLI to update package.json and manage remote merging.

Can I automatically create a Git tag and merge a feature branch into the main branch?

Yes, you can automatically create a Git tag and merge a feature branch into the main branch. The Skill analyzes your commit history, applies the correct version bump, and handles the remote merge using the GitHub CLI.

Do I need Node.js and the GitHub CLI to automate Git releases?

Yes, Node.js and the GitHub CLI are required dependencies for automating Git releases. Node.js updates the package.json version, while the GitHub CLI handles remote repository operations like pushing tags and merging branches.

How does automated versioning determine patch, minor, or major release increments?

Automated versioning determines patch, minor, or major release increments by parsing conventional commit messages. The Skill inspects your commit history to intelligently decide the correct semantic version bump before creating the release tag.

What is the best way to prepare a release from a merge branch?

The best way to prepare a release from a merge branch is to run the Skill against your current branch. It will analyze commits, bump the package version, create a Git tag, and push the merge to your main remote branch automatically.

Are there limitations when using automated Git tagging for deployment?

Limitations include strict reliance on conventional commit message formatting for accurate version bumping, and the necessity of having Git, Node.js, and the GitHub CLI properly configured in your local environment to execute remote operations.