pr-create

Create GitHub pull requests with conventional titles and structured bodies.

2|1|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/proven-xyz/proven-app --skill pr-create-proven-xyz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-create
Source: https://github.com/proven-xyz/proven-app/tree/main/.agents/skills/pr-create
Command: npx skills add https://github.com/proven-xyz/proven-app --skill pr-create-proven-xyz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically generate GitHub pull requests with properly formatted titles that pass the check-pr-title CI validation, removing manual title tuning and review delays.

Core Features & Use Cases

  • Automatically format PR titles to conform to project conventions and CI checks.
  • Generate structured PR bodies that provide clear context for reviewers.
  • Trigger PR creation via intents like /pr or /pr-create or natural language prompts.

Quick Start

Prompt me to create a PR with a conventional title and descriptive body, and I will carry out the PR creation.

Frequently Asked Questions about pr-create

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

FAQPage Schema
How do I format a GitHub pull request title to pass CI validation?

PR title formatting relies on conventional commit standards to satisfy check-pr-title CI rules. This approach automatically generates machine-checkable titles that pass validation, removing manual title tuning and preventing CI failures during pull request creation.

How do I automatically create a pull request with a structured body on GitHub?

Automatically create GitHub pull requests by triggering intents like /pr or /pr-create. This generates structured PR bodies with clear reviewer context and conventional titles, executing creation via GitHub CLI or API calls without manual formatting.

Why does my pull request fail the check-pr-title CI check?

Pull requests fail check-pr-title CI checks when titles do not conform to repository conventions. Automatic title formatting applies the required conventional structure to ensure your PR metadata passes validation and avoids review delays.

Can I create a GitHub pull request from a feature branch using the GitHub CLI?

Yes, you can create a GitHub pull request from a feature branch using GitHub CLI. The workflow formats conventional titles and structured bodies, then triggers automated PR creation via CLI or API calls to satisfy CI validation.

What is the best way to generate PR metadata for development workflows?

The best way to generate PR metadata for development workflows is automated formatting that applies conventional title structures. This produces machine-checkable PR titles and structured bodies that pass check-pr-title validation and provide clear reviewer context.