create-pr

Create GitHub pull requests with ticket references and Markdown descriptions.

7|Updated May 9, 2014
One-click install
npx skills add https://github.com/pjcj/base --skill create-pr-pjcj
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/pjcj/base/tree/main/.claude/skills/create-pr
Command: npx skills add https://github.com/pjcj/base --skill create-pr-pjcj

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create GitHub pull requests that consistently reference the associated ticket, ensuring traceability and clear context for reviewers.

Core Features & Use Cases

  • Generate PRs from the current branch using the gh CLI, enforcing ticket-based titles.
  • Ensure PR descriptions include issue references, scope, and implications.
  • Apply standard formatting and conventions for easy review and automation.

Quick Start

Tell the assistant to create a PR for the current branch using gh, ensuring the title starts with the ticket ID.

Frequently Asked Questions about create-pr

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

FAQPage Schema
How do I automate GitHub pull requests with ticket references using gh CLI?

Automate GitHub pull requests by using the gh CLI to publish branches, enforcing ticket ID extraction from GH-XXXX branch names to generate titles and Markdown descriptions with issue links. This ensures traceability and clear context for code review.

What is the required branch naming convention for automated PR creation?

The required branch naming convention for automated PR creation is the GH-XXXX format. This allows the workflow to extract the ticket ID automatically, format the PR title accordingly, and link the originating issue in the description.

How to format PR descriptions for code review and approval?

Format PR descriptions for code review by generating a structured Markdown body containing a summary, changes, implications, and linkage to the originating issue. This standard formatting ensures clear context and scope for reviewers.

Does this automated PR workflow work without additional GitHub dependencies?

This automated PR workflow operates without additional dependencies, relying solely on the gh CLI to publish pull requests. It extracts ticket IDs, formats titles, and generates structured descriptions directly through the command line interface.

Why does my GitHub PR need a structured description with issue linkage?

A GitHub PR needs a structured description with issue linkage to ensure traceability and provide clear context for reviewers. By referencing the originating ticket and detailing implications, the review process is streamlined and approvals are easier to track.

Can I generate pull requests with standard formatting and conventions automatically?

Generate pull requests with standard formatting and conventions automatically by applying this workflow to GH-XXXX branches. It enforces ticket-based titles and creates structured Markdown descriptions, ensuring consistency for easy review and automation.