releasepr

Configure and troubleshoot automated GitHub release pull request workflows.

182|8|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/compozy/agh --skill releasepr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: releasepr
Source: https://github.com/compozy/agh/tree/main/.agents/skills/releasepr
Command: npx skills add https://github.com/compozy/agh --skill releasepr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

releasepr removes the guesswork of configuring and operating an automated “release pull request” flow in a consuming GitHub repository, so releases happen reliably and repeatably.

Core Features & Use Cases

  • Release PR onboarding for consumers: install the pr-release CLI, wire the GitHub Actions workflow, and set up the required token and permissions.
  • Configuration and lifecycle guidance: author and validate a correct .pr-release.yaml (including release_artifacts and environment-variable behavior) and understand the release-PR → dry-run → production-release pipeline.
  • Conventional-commit and failure troubleshooting: apply commit conventions for semantic versioning and debug common CI/config errors using the skill’s reference router.

Quick Start

Ask an agent to prepare your repo for release automation by configuring .pr-release.yaml and the GitHub Actions release workflow, then run a read-only setup check to confirm everything is wired correctly.

Frequently Asked Questions about releasepr

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

FAQPage Schema
How do I automate GitHub release pull requests using conventional commits?

Automate GitHub release pull requests by configuring a .pr-release.yaml file and GitHub Actions workflow to trigger release PRs from conventional commit messages for semantic versioning.

What is the lifecycle of an automated release PR in a CI workflow?

The automated release PR lifecycle follows a strict sequence: generating a release pull request, merging it, and then triggering the production release to complete the semantic versioning pipeline.

How do I set up the pr-release CLI for first-time onboarding in my repository?

Set up the pr-release CLI by installing the tool, wiring the GitHub Actions workflow, and configuring required token permissions to enable automated release pull request creation in your repository.

Why is my GitHub Actions release workflow failing after updating .pr-release.yaml?

GitHub Actions release workflow failures after .pr-release.yaml changes often stem from incorrect environment variable behavior or invalid configuration, which you can debug using a read-only verification check.

Do I need conventional commits for semantic versioning with release automation?

Yes, conventional commits are required for semantic versioning with release automation because they drive the version bump logic and release notes generation within the automated workflow.

Can I verify my release automation configuration without pushing changes?

Yes, you can verify release automation configuration without pushing changes by running a safe read-only setup check to confirm your .pr-release.yaml and GitHub Actions workflow are wired correctly.