pr-creator

Creates spec-linked, traceability-verified pull requests via the gh CLI.

Updated May 21, 2026
One-click install
npx skills add https://github.com/CagesThrottleUs/private-ai-harness --skill pr-creator-cagesthrottleus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-creator
Source: https://github.com/CagesThrottleUs/private-ai-harness/tree/main/skills/pr-creator
Command: npx skills add https://github.com/CagesThrottleUs/private-ai-harness --skill pr-creator-cagesthrottleus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Pull requests often go out with non-compliant titles, missing spec or plan references, no traceability to requirements, and no review verdict, making them unverifiable and hard to audit. This Skill enforces a gated, step-by-step PR creation workflow so every PR is spec-linked, plan-linked, commit-msg compliant, and review-verified before it reaches GitHub. ## Core Features & Use Cases - Pre-flight Gates: Verifies a clean working tree, up-to-date branch, passing build and tests, and commit-msg.sh compliant commits before proceeding. - Spec and Plan Enforcement: Blocks PR creation unless a spec file with a valid spec_id and a plan file are provided, then auto-extracts requirement IDs and the north-star metric. - Auto-Traceability: Greps the diff for @spec_id and @req_id annotations, builds a traceability table, and flags missing annotations as gaps that force a draft PR. - Review Verdict Consumption: Reads the review summary written by the finishing-a-development-branch workflow and maps MERGE READY, NEEDS WORK, or BLOCKED verdicts to ready, draft, or stop outcomes. - Use Case: After finishing a feature branch, run the Skill to generate a compliant title and WHY-focused body, validate them against commit-msg.sh, assign CODEOWNERS-based reviewers, and create the PR with gh pr create as draft or ready. ## Quick Start Create a pull request for my current branch using the pr-creator workflow, linking it to the spec and plan in the .ai directory.

Frequently Asked Questions about pr-creator

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

FAQPage Schema
How do I create a pull request with the gh CLI?

Use gh pr create with --title, --body, --base, and --head flags after validating the branch state. This Skill automates that flow by generating a compliant title and WHY-focused body, then running gh pr create as draft or ready based on gate results.

How do I enforce spec and plan linkage on pull requests?

Require each PR to reference a spec file with a valid spec_id and a plan file before creation. The Skill blocks PR creation entirely when either artifact is missing, ensuring every PR is verifiable against a baseline.

What pre-flight checks should run before opening a PR?

Verify the working tree is clean, the branch is not behind or diverged from main, the build passes, tests pass, and all commit messages comply with the project's commit-msg.sh rules. Any failure stops the process with a report of what to fix.

When is a pull request created as a draft instead of ready?

A PR becomes a draft when traceability gaps exist in the diff, the review verdict is NEEDS WORK, or pre-flight produced warnings. It is created ready only when pre-flight is clean, traceability coverage is full, and the verdict is MERGE READY.

Why does PR creation stop with a BLOCKED review verdict?

A BLOCKED verdict from the branch review summary means critical issues exist that must be fixed before submission. The Skill consumes that verdict and refuses to create the PR rather than re-running review agents.