pr-creation

Create GitHub pull requests after Final Gate approval with validation and branch management.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates end-to-end pull request creation with validation, branch management, and automated PR formatting after a feature is approved.

Core Features & Use Cases

  • Pre-push validation, ensuring code quality before PR creation.
  • Feature-branch orchestration, pushing changes to origin feature branches.
  • Automated PR creation with properly formatted metadata and a PR URL returned.

Quick Start

Create a PR automatically after Ship and Final Gate approval by providing a feature branch and an optional PR title.

Frequently Asked Questions about pr-creation

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

FAQPage Schema
How do I automate GitHub pull request creation with branch management?

Automate GitHub pull request creation by orchestrating feature branches, running pre-push validation, and executing `gh pr create` to publish formatted metadata and return a PR URL.

What is validated before a feature branch is pushed to origin for a PR?

Pre-push validation ensures code quality through pre-commit checks before pushing changes to an origin feature branch, maintaining main-branch invariants within a worktree context.

Do I need the gh CLI to automate pull request workflows?

Yes, you need access to `gh pr create` to publish pull requests automatically. The workflow requires a valid feature branch, pre-commit checks, and Final Gate approval before execution.

How do I format PR metadata automatically after feature approval?

PR metadata is formatted automatically during creation by providing a feature branch and an optional PR title after Ship and Final Gate approval, returning a direct PR URL.

What are the limitations of automated PR creation in a worktree context?

Automated PR creation requires strict adherence to main-branch invariants within a worktree context. It depends on pre-commit checks passing and will not execute without Final Gate approval.