pr-create

Push the current branch and create or update a GitHub pull request from a branch plan.

2|Updated Apr 7, 2026

Search Tags:#automation #git #github #branch #pr #pull-request #branch-plan

Ready to run

npx skills add https://github.com/soumyaray/ray-ai-skills --skill pr-create-soumyaray

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pr-create
Source: https://github.com/soumyaray/ray-ai-skills/tree/main/ray-pr-create
Command: npx skills add https://github.com/soumyaray/ray-ai-skills --skill pr-create-soumyaray

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates pushing the current feature branch and creating or updating a GitHub pull request with a structured description derived from the branch plan, saving time drafting PR notes and ensuring consistency.

Core Features & Use Cases

Detect base branch automatically or via user input.
Create a draft PR if none exists, or update an existing PR for the branch.
Read and derive PR content from a PLAN.<branch>.md branch plan, including goals and tasks.
Push the branch to the remote (git push -u origin HEAD).
Use gh pr create / gh pr edit to manage PR title and body.

Quick Start

Run the pr-create command to push the current branch and create a draft PR with a description derived from the branch plan.

Frequently Asked Questions about pr-create

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 branch plan?▼

You can generate a pull request description by reading a PLAN.<branch>.md file referenced in CLAUDE.local.md, extracting goals and tasks, then using gh pr commands to assemble the PR title and body automatically.

What's the best way to push a Git branch and create a draft PR at the same time?▼

The best way to push a branch and create a draft PR simultaneously is running an automated workflow that executes git push -u origin HEAD, then uses gh pr create to open a draft pull request with a structured description.

Can I update an existing GitHub pull request without creating a duplicate?▼

Yes, you can update an existing GitHub pull request without duplicates by detecting if a PR already exists for the branch and using gh pr edit to modify the title and body instead of calling gh pr create again.

How does auto-detection of the base branch work when creating a PR?▼

Auto-detection of the base branch works by identifying the target branch automatically from the Git workflow context, or falling back to user input if the base branch cannot be determined confidently.

Do I need a specific file format to structure my PR content?▼

Yes, you need a PLAN.<branch-name>.md markdown file to structure your PR content. This file must be referenced in CLAUDE.local.md so the workflow can extract goals and tasks to populate the PR title and body.

What are the limitations of automating PR creation from a branch plan?▼

Limitations include requiring a pre-existing PLAN.<branch>.md file and CLAUDE.local.md reference, dependency on gh CLI and git commands, and restriction to GitHub workflows where plan-driven PR descriptions are needed.