create-pr

Automate GitHub pull request creation with preflight gates and evidence collection.

29|5|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/johnqtcg/awesome-skills --skill create-pr-johnqtcg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/johnqtcg/awesome-skills/tree/main/skills/create-pr
Command: npx skills add https://github.com/johnqtcg/awesome-skills --skill create-pr-johnqtcg

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pyyaml, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Create evidence-backed pull requests to the GitHub main branch with strict preflight, quality, and security gates. Use when users ask to create/submit/open/update a PR to main (including private repos), decide draft vs ready state, and provide reviewer-ready context for team review.

Core Features & Use Cases

  • Gate A–H sequence enforcement with evidence collection (preflight, quality, security gates)
  • PR body generation with structured evidence and risk disclosures
  • Ready/draft decision based on gate outcomes and suppression rules
  • Self-checks for branch protection, conflicts, and policy compliance

Quick Start

Run the bundled script to execute Gate A–H, generate a reviewer-ready PR body, and submit or update a PR against main.

Frequently Asked Questions about create-pr

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

FAQPage Schema
How do I automate pull request creation with required gate checks on GitHub?

Automating pull request creation with gate checks involves running a preflight workflow that enforces quality and security gates sequentially, collecting evidence for each check before submitting the PR to a protected main branch.

What is the best way to generate a PR body with test evidence and risk disclosures?

Generating a PR body with test evidence requires computing change risk and gathering regression test results during the preflight sequence, then structuring those disclosures into a reviewer-ready format for the team.

How do I decide if a pull request should be a draft or ready for review?

Deciding if a pull request is ready for review depends on evaluating gate outcomes and suppression rules; if preflight, security scans, or dependency checks fail, the PR is submitted as a draft until issues are resolved.

Does this automated PR workflow work with branch protection rules on private repositories?

Yes, this automated PR workflow supports private repositories by performing self-checks for branch protection compliance, conflict detection, and policy enforcement before attempting to push changes or open a pull request.

What security checks are required before opening a pull request to a protected main branch?

Required security checks before opening a pull request to a protected main branch include secret scanning and dependency checks, which are enforced as part of the gate sequencing process alongside quality and preflight validations.

Why does my automated pull request fail the preflight gate sequence?

An automated pull request fails the preflight gate sequence when computed change risk, test evidence, security scans, or dependency checks do not meet the strict policy compliance requirements enforced for protected main branches.