skills.rest
creepyblues
creepybluesCOMMUNITY
Explore all skills by this author →
GitHub

pr-production

Generate a production pull request from v2 to main with change summaries and deployment checklists.

Updated Jul 22, 2025
Search Tags:#automation#git#workflow#production#staging#pr#pull-request
One-click install
npx skills add https://github.com/creepyblues/kstorybridge-integrated --skill pr-production
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-production
Source: https://github.com/creepyblues/kstorybridge-integrated/tree/main/.claude/skills/pr-production
Command: npx skills add https://github.com/creepyblues/kstorybridge-integrated --skill pr-production

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the promotion of staging changes from v2 to production by generating a production-grade pull request that includes a change summary, affected apps, and a deployment checklist.

Core Features & Use Cases

  • Auto-generates a production PR title and body with a per-app changes overview.
  • Performs pre-flight checks (branch alignment, clean working directory, up-to-date v2).
  • Provides a deployment checklist and rollback guidance for safe promotion of v2 to main.

Quick Start

Run the pr-production workflow on a repository with a v2 branch to auto-generate and open a production PR from v2 to main, including a change summary and deployment checklist.

Frequently Asked Questions about pr-production

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

FAQPage Schema
How do I automate a production pull request from a staging branch?▼

You automate a production pull request by running a workflow that promotes staging changes into a production PR, auto-generating a detailed body with change summaries, affected apps, and a deployment checklist for the v2 to main merge.

What pre-flight checks are needed before promoting staging to main?▼

Pre-flight checks for promoting staging to main include verifying branch alignment, ensuring a clean working directory, and confirming the v2 branch is up-to-date before generating the production pull request.

Can I generate a deployment checklist and rollback guidance in a GitHub PR?▼

Yes, the workflow auto-generates a GitHub PR body that includes a deployment checklist and rollback guidance, providing a per-app changes overview to safely promote v2 changes into production.

Do I need git and GitHub CLI to automate v2 to main release workflows?▼

Yes, you need git and GitHub CLI access to automate v2 to main release workflows, as the PR generation relies on repository conventions and command-line operations to create and open the production pull request.

How does automatic PR body generation work for affected apps?▼

Automatic PR body generation detects affected apps from the staging changes and compiles per-app change counts, creating a structured summary within the production pull request body for clear release tracking.

Related Skills

Explore More Software Engineering Skills→
MINT-IAMINT-IA

mint-commit

Enforce standardized git commit and promotion workflows with branch and merge rules.

Official
Advanced
CODE-SAURABHCODE-SAURABH
2

land-and-deploy

Merge approved pull requests and verify production health after deployment.

Community
Advanced
Nairon-AINairon-AI
7

flux-gate

Validate staging deployments and generate promotion pull requests.

Official
Advanced
NVIDIANVIDIA
3.4k

release-cherry-pick

Cherry-pick labeled merged pull requests into release branches via GitHub CLI.

Official
Advanced