pr-create

Create GitHub pull requests with summaries, test plans, and linked issues.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines GitHub workflows by automatically generating well-structured pull requests from code changes, including concise summaries, test plans, and issue linkages.

Core Features & Use Cases

  • Analyze changes in the current branch and categorize them (feat, fix, docs, chore).
  • Draft PR title and body with a clear summary, test plan, and linked issues.
  • Create PR via the gh CLI, push branches when needed, and apply labels and reviewers.
  • Link related issues and ensure repository conventions are followed for consistent PR metadata.

Quick Start

Draft a review-ready PR for the current branch with a concise summary, test plan, linked issues, and reviewer assignments.

Frequently Asked Questions about pr-create

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

FAQPage Schema
How do I automate GitHub pull request creation from code changes?

Automating GitHub pull request creation involves analyzing current branch changes and generating a structured PR with summaries, test plans, and linked issues. This Skill uses the gh CLI to push branches, apply labels, assign reviewers, and create review-ready pull requests automatically.

How do I generate a standardized pull request summary and test plan?

Generating a standardized pull request summary involves categorizing branch changes into feat, fix, docs, or chore types. This Skill drafts a structured PR body with a concise summary, test plan, and issue linkages to ensure consistent repository conventions and review-ready documentation.

Do I need the gh CLI to create pull requests and link issues automatically?

Yes, you need the gh CLI installed to create pull requests and link issues automatically. This Skill requires both git and the gh CLI to push branches, apply labels, assign reviewers, and execute the PR creation workflow from your current branch.

Can I apply labels and assign reviewers when creating a PR from the current branch?

Yes, you can apply labels and assign reviewers when creating a PR from the current branch. This Skill leverages the gh CLI to push the current branch, create the pull request, and configure metadata like labels and reviewer assignments during the automated generation process.

What is the best way to ensure consistent PR metadata and follow repository conventions?

The best way to ensure consistent PR metadata is to automate the drafting process with standardized summaries, test plans, and issue linkages. This Skill analyzes code changes, categorizes them, and structures the PR body to follow repository conventions for consistent metadata.

Why does automated branch management and PR creation categorize changes into feat, fix, docs, or chore?

Automated branch management and PR creation categorize changes into feat, fix, docs, or chore to generate clear, structured summaries. This categorization helps standardize PR metadata, link related issues, and ensure reviewers understand the nature of the code changes quickly.