pr-creation

Creates and updates GitHub pull requests with an iterative compress-critique-fix review loop.

64|11|Updated May 24, 2026
One-click install
npx skills add https://github.com/AlexanderMattTurner/agent-glovebox --skill pr-creation-alexandermattturner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-creation
Source: https://github.com/AlexanderMattTurner/agent-glovebox/tree/main/.claude/skills/pr-creation
Command: npx skills add https://github.com/AlexanderMattTurner/agent-glovebox --skill pr-creation-alexandermattturner

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Opening a pull request involves far more than running gh pr create: sizing the diff, searching for prior work, writing a reviewer-friendly description, self-critiquing the change, and driving CI to green. This Skill encodes that entire workflow so every PR follows the same disciplined process instead of ad-hoc habits. ## Core Features & Use Cases - Footprint bounding and batching: Combines small changes onto one branch under a ~50-file bound, partitions batched work into one Conventional Commit per concern, and splits or chains PRs when the bound is exceeded. - Compress-critique-fix loop: Launches a self-critique pass (via the bundled critique prompt) covering dead code, readability, reuse, tests, correctness, and scope before submission, iterating until a pass finds nothing. - Prior-art and ownership checks: Searches the tree, issue list, and open PRs before branching, respects live-ownership labels, and files claim issues for shared defects to avoid duplicate work. - Template-driven PR bodies: Generates Conventional Commit titles and structured bodies (What & why, Decisions made, Proposed guards, Review focus) with web-session-safe gh api and MCP fallbacks when gh pr commands are blocked. - Use Case: After finishing a feature branch, ask the agent to open the PR; it pushes once, opens a draft, runs the critique loop, writes the description, and watches CI without ever merging without explicit instruction. ## Quick Start Create a pull request for my current branch following the pr-creation workflow.

Frequently Asked Questions about pr-creation

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

FAQPage Schema
How do I create a pull request with an AI coding agent?

Invoke the pr-creation skill after committing work to a feature branch. It pushes the branch, opens a draft PR with a Conventional Commit title and structured body, runs a self-critique loop, and monitors CI until checks pass.

How should I batch multiple small changes into one pull request?

Combine changes onto one branch while it stays under roughly 50 changed files, giving each separable concern its own Conventional Commit. Small changes under ~50 lines should be carried until about four accumulate, unless one must land urgently.

What do I do when gh pr create returns HTTP 403 in a web session?

Web sessions block GraphQL-backed gh pr commands. Use the REST replacements: gh api for listing, viewing, and editing PRs, and the GitHub MCP create_pull_request tool for creation, as documented in the pr-templates reference.

Can this skill merge a pull request automatically?

No. The skill never merges without a direct, explicit user instruction naming the PR. When instructed, it enables auto-merge and records the consent in the PR body, but required checks still gate the actual merge.

When should a large branch be split into multiple PRs?

Split when the branch exceeds roughly 50 changed files, when a change must land on its own timeline, or when the diff is too large to review coherently. Dependent pieces become a chain of PRs, each layered on the parent branch.