create-pr

Automates GitHub pull request creation from branch to main using gh pr create.

4|1|Updated Jan 8, 2024
One-click install
npx skills add https://github.com/OpenSourcePharmaFoundation/ospf-ayurveda-kg --skill create-pr-opensourcepharmafoundation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/OpenSourcePharmaFoundation/ospf-ayurveda-kg/tree/main/.claude/skills/create-pr
Command: npx skills add https://github.com/OpenSourcePharmaFoundation/ospf-ayurveda-kg --skill create-pr-opensourcepharmafoundation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It saves time and effort by automatically generating a professional pull request title and description based on what changed between your current branch and main.

Core Features & Use Cases

  • Git diff analysis: Reviews commit history and file changes relative to main to understand what you did.
  • PR description drafting: Produces a structured PR body including summary, key changes, testing guidance (when applicable), and related issues.
  • Auto PR creation via GitHub CLI: Creates the pull request using gh pr create with a concise final body, ready for review.

Quick Start

Use the create-pr skill to open a pull request from your current branch to main with an automatically generated, concise description based on the changes you made.

Frequently Asked Questions about create-pr

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

FAQPage Schema
How do I automatically generate a pull request description from a git diff?

You can automatically generate a pull request description by analyzing git branch differences and commit history relative to main, producing a structured PR body with a summary and key changes.

Can I create a GitHub pull request from the command line with an automatically generated title and body?

Yes, you can create a GitHub pull request using the gh pr create command, which uses a generated title and a concise body derived from analyzing your current branch's file changes.

What is the best way to draft a structured pull request body for code review workflows?

Drafting a structured pull request body involves a two-pass process that first details branch differences and then simplifies them into a summary, key changes, and testing guidance for reviewers.

Do I need the GitHub CLI installed to automate pull request creation from a feature branch?

Yes, you need the GitHub CLI installed because the automation executes the gh pr create command to open the pull request directly from your current feature branch to main.

Does automated PR generation include testing notes and related issues in the final description?

Automated PR generation includes testing guidance when applicable and lists related issues, ensuring the final pull request description provides complete context for the code review.

Will the automated pull request summary add auto-generated tags to the GitHub PR?

No, the automated pull request summary does not add auto-generated tags, ensuring the GitHub PR title and body remain clean and only contain the analyzed change details.