pr-production

Finalize release candidate versions and create a production pull request from staging to master.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/lety-ai/lety-skill-hub --skill pr-production-lety-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-production
Source: https://github.com/lety-ai/lety-skill-hub/tree/main/plugins/pr-production/skills/pr-production
Command: npx skills add https://github.com/lety-ai/lety-skill-hub --skill pr-production-lety-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enforces a safe, auditable promotion of a release candidate from staging to production, reducing manual errors when finalizing versions, pushing changes, and opening the production pull request.

Core Features & Use Cases

  • Protected branch guard and validation: prevents execution from non-staging branches and stops if there are no commits ahead of master.
  • Version detection and finalization: locates the repository version file, validates that it is a release candidate (RC), and strips the RC suffix to produce a stable version.
  • Commit analysis and PR composition: analyzes commits and diffs against origin/master, generates a structured release PR body grouped by change type, checks for existing PRs, and uses gh CLI for PR operations with explicit user approvals.
  • Use Case: When a release candidate in staging is ready for production, use this Skill to validate the RC, finalize the version file, push staging, and create a production PR with a complete changelog and checklist.

Quick Start

Run this skill from the staging branch to validate the RC version, finalize the version file, push staging, and create the production PR to master after confirming each step.

Frequently Asked Questions about pr-production

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

FAQPage Schema
How do I create a production release PR from staging to master in a GitFlow workflow?

To create a production release PR, you run this Skill from your staging branch to validate the release candidate version, strip the RC suffix, and push staging to open a structured pull request to master using the gh CLI.

How do I finalize a release candidate version before opening a production pull request?

Finalizing a release candidate version involves locating the repository version file, validating its RC status, and stripping the RC suffix to produce a stable version before committing and pushing the finalized release.

What do I need to automate production release PRs with the GitHub CLI and GitFlow?

You need a synced git remote, an authenticated gh CLI for pull request operations, a detectable version file in the repository, and explicit user approvals for commit, push, and PR creation.

Does creating a production release PR require commits to be ahead of master?

Yes, the production release PR creation includes a protected branch guard that stops execution if it detects no commits ahead of master, ensuring the release PR contains actual changes.

How are release commits analyzed and grouped when generating a PR body?

Commits and diffs are analyzed against origin/master to generate a structured release PR body, grouping changes by type to provide a complete changelog and release checklist.

Why does my release PR creation fail when running from a non-staging branch?

Release PR creation fails on non-staging branches due to a protected branch guard that prevents execution, ensuring the GitFlow workflow only promotes release candidates from the correct staging environment.