pr-orchestrator

Opens or updates GitHub pull requests with gated validation and issue close-out.

Updated Jul 29, 2026
One-click install
npx skills add https://github.com/chris-prener/dev-kit --skill pr-orchestrator-chris-prener
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-orchestrator
Source: https://github.com/chris-prener/dev-kit/tree/main/dev-kit/skills/pr-orchestrator
Command: npx skills add https://github.com/chris-prener/dev-kit --skill pr-orchestrator-chris-prener

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Opening a pull request involves repetitive coordination: composing a consistent PR body, running code review, checking the changelog, verifying QC, and closing referenced issues with retrospectives. This Skill automates that entire pre-merge workflow so nothing is forgotten. ## Core Features & Use Cases - Create and update modes: Detects whether the branch already has an open PR and either creates a new one or refreshes the managed body sections while preserving operator-written content. - Three validation gates: Runs code review, changelog verification, and QC checks from reference files, halting on blockers and supporting opt-out markers where allowed. - Issue close-out: After the PR exists, posts a retrospective on each closed issue and transitions any linked implementation plan to shipped status. - Use Case: After finishing a feature branch that closes two issues, ask to open a PR; the Skill composes the five-section body, runs all gates, creates the PR via the GitHub CLI, and closes both issues with retrospectives. ## Quick Start Open a pull request for my current branch and close the issues it resolves.

Frequently Asked Questions about pr-orchestrator

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

FAQPage Schema
How do I open a GitHub pull request with automated checks?▼

Invoke the skill with a phrase like "open pr" or "ship the branch" on a pushed feature branch. It composes a five-section PR body, runs code review, changelog, and QC gates, then creates the PR with gh pr create.

How do I update an existing pull request body without regenerating everything?▼

Re-run the skill on a branch that already has an open PR and it dispatches to update mode. Only the Closes section and the updated timestamp regenerate; your manually written prose outside the managed fence is preserved verbatim.

Can I skip the changelog or QC gates for a pull request?▼

Yes, add a _no-changelog: <justification>_ or _no-prep-gate: <justification>_ marker in the PR body's Notes section. The code review gate is mandatory and has no opt-out marker.

What happens when a PR gate returns a blocker?▼

The skill halts immediately, displays the gate's findings, and does not create or update the PR or run the retrospective step. You fix the findings locally and re-invoke, or choose an explicit alternative offered by the gate.

Does this skill review or merge pull requests?▼

No, reviewing and merging happen on github.com and are explicitly out of scope. The skill only opens or updates PRs, runs pre-PR validation gates, and closes referenced issues with retrospectives.