create-pr

Automate pull request creation in GitHub repositories via the GitHub CLI.

1|Updated Apr 17, 2025
One-click install
npx skills add https://github.com/carrot-foundation/schemas --skill create-pr-carrot-foundation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/carrot-foundation/schemas/tree/main/.cursor/skills/create-pr
Command: npx skills add https://github.com/carrot-foundation/schemas --skill create-pr-carrot-foundation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the pull request creation workflow for changes that are ready for review, ensuring a consistent and verified PR process.

Core Features & Use Cases

  • Pre-flight checks: validate that quality gates pass before PR creation.
  • Branch and change analysis: inspect commits since diverging from main to inform the PR description.
  • PR metadata guidance: enforce clear PR titles and bodies and provide a standardized description template.
  • PR creation automation: push a ready branch and create the PR using GitHub CLI with proper labels and linking issues as needed.

Quick Start

Push your feature branch after all checks pass and open a PR with a clear title and detailed description.

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 GitHub CLI?

Automating pull request creation involves pushing your feature branch and using the GitHub CLI to open a PR with validated metadata, enforced titles, and linked issues.

What pre-flight checks are needed before opening a pull request?

Pre-flight checks for pull requests validate that quality gates pass and branch requirements are met before pushing changes to ensure a consistent and verified PR process.

How do I generate a standardized PR description from branch commits?

Generating a standardized PR description requires analyzing commits since diverging from main to inform the PR body, enforcing a clear title and structured template for consistency.

Can I validate PR size and metadata before pushing a feature branch?

Yes, you can validate PR size and metadata by applying branch checks and change analysis before creation, ensuring quality gates pass and descriptions meet standards.

What are the limitations of automating branch management for pull requests?

Limitations of automating branch management include dependency on the GitHub CLI environment and the necessity for manual post-creation steps to fulfill remaining quality-gate requirements.