create-pr

Create GitHub pull requests with auto-generated titles and bullet-point bodies.

223|68|Updated Aug 18, 2025
One-click install
npx skills add https://github.com/Melvynx/aiblueprint --skill create-pr-melvynx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/Melvynx/aiblueprint/tree/main/claude-code-config/skills/git-create-pr
Command: npx skills add https://github.com/Melvynx/aiblueprint --skill create-pr-melvynx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual pull request creation is time-consuming and prone to inconsistent descriptions. This Skill automates the generation and submission of GitHub PRs with concise titles and structured bodies, reducing overhead and ensuring consistency across teams.

Core Features & Use Cases

  • Auto-generated PR title and body derived from current commits and diffs
  • Branch safety: guides and enforces descriptive branch naming and prevents unsafe merges
  • Push and publish: uses gh pr create to open PRs and returns the PR URL for quick sharing

Quick Start

Prompt the AI to create a PR for the current branch with a descriptive title and a structured body listing changes. Example: Create PR from feature/new-auth to main with title "Add OAuth login" and body detailing the implemented endpoints, UI changes, and tests.

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 request creation from a feature branch?

Automating GitHub pull request creation involves generating a PR title under 72 characters and a structured bullet-point body from current branch commits and diffs, then publishing via the gh pr create command to return a shareable PR URL.

What is the best way to generate a PR title and description from my Git commits?

Generating a PR title and description from Git commits is best handled by automatically deriving a title under 72 characters and a structured bullet-point body from the current branch diffs and commit history to ensure consistency across teams.

Does this PR automation tool enforce branch naming conventions before opening a pull request?

Yes, this PR automation tool enforces branch safety by guiding and requiring descriptive branch naming conventions to prevent unsafe merges before you create and push the GitHub pull request.

Can I auto-detect the base branch when creating a GitHub pull request?

You can auto-detect the base branch when creating a GitHub pull request because the Skill automatically identifies the target branch, generates the title and body, and executes the gh pr create command to publish your code changes.

Why should I automate pull request generation instead of writing descriptions manually?

You should automate pull request generation because manual creation is time-consuming and prone to inconsistent descriptions, whereas automation ensures concise titles and structured bodies derived directly from your commits and diffs.