pr-to-production

Create a Linear release ticket and GitHub pull request merging the default branch into production.

Updated May 20, 2026
One-click install
npx skills add https://github.com/paywhereb/paywhere-claude-plugins --skill pr-to-production
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-to-production
Source: https://github.com/paywhereb/paywhere-claude-plugins/tree/main/paywhere-eng-workflow/skills/pr-to-production
Command: npx skills add https://github.com/paywhereb/paywhere-claude-plugins --skill pr-to-production

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of reliably creating a production release PR and corresponding Linear release ticket, including an accurate summary of the exact set of commits being merged.

Core Features & Use Cases

  • Release PR creation from commit range: Computes the authoritative list of non-merge commits between the default branch and production, aborting if production is already up to date.
  • Linear ticket with consistent release summary: Creates a release-labeled Linear issue using the same release-style summary and change list that will appear in the PR body.
  • Duplicate prevention: Checks for an existing open release PR for the same head/base pair and reports it instead of creating a second ticket/PR.
  • Use case: When you’re ready to promote work from main to production, this Skill opens the right Linear ticket and a PR that documents exactly what will be shipped (commit list plus grouped summary).

Quick Start

Run the pr-to-production skill after configuring your repo’s .claude/eng-workflow.json and authenticating with Linear and GitHub/gh so it can create the ticket and PR for the default branch into production.

Frequently Asked Questions about pr-to-production

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

FAQPage Schema
How do I create a production release PR with an accurate commit list from a default branch?

You can automate creating a production release PR by computing the authoritative list of non-merge commits between the default branch and production, then opening a GitHub pull request that documents the exact changes being shipped.

How does branch promotion prevent duplicate open release pull requests?

Branch promotion prevents duplicate release PRs by checking for an existing open pull request for the same head and base pair, reporting the duplicate instead of creating a second ticket or PR.

How do I automate Linear ticket creation for a GitHub release workflow?

You can automate Linear ticket creation by using the save_issue tool to generate a release-labeled issue containing the same release-style summary and grouped change list that will appear in the GitHub PR body.

Do I need a specific configuration file to enable engineering workflow guard checks for releases?

Yes, you need to configure your repository's eng-workflow.json file to define team and branch parameters, which the system reads to verify guard enablement before proceeding with release promotion.

What happens if the production branch is already up to date with the default branch?

If the production branch is already up to date with the default branch, the commit-range enumeration finds no changes and the release promotion process aborts without creating a pull request or Linear ticket.

Can I use gh pr create to merge a default branch into production with a release summary?

Yes, the workflow uses gh pr create to open a release-grade pull request merging the default branch into production, generating a grouped summary of the exact non-merge commits being shipped.