pr-submit

Create a GitHub pull request from the current working branch and return its URL.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/sahilrajput280/DOGRAH --skill pr-submit-sahilrajput280
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-submit
Source: https://github.com/sahilrajput280/DOGRAH/tree/main/pipecat/.claude/skills/pr-submit
Command: npx skills add https://github.com/sahilrajput280/DOGRAH --skill pr-submit-sahilrajput280

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Submitting changes to a GitHub repository typically involves several steps: creating a branch, staging and committing changes, pushing to the remote, and opening a pull request. This Skill streamlines that workflow by turning your current working branch into a GitHub PR with minimal commands, accelerating code reviews and merging.

Core Features & Use Cases

  • Create a pull request from the current branch to the repository's default base branch.
  • Push local commits and ensure upstream tracking for seamless collaboration.
  • Return the PR URL for quick sharing and review coordination.
  • Use case: a developer finishes a small feature or bug fix on a feature branch and wants to open a PR rapidly for team feedback.

Quick Start

Create and push a pull request from the current branch to the repository's default base branch.

Frequently Asked Questions about pr-submit

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

FAQPage Schema
How do I create a GitHub pull request from my current branch with one command?

To create a GitHub pull request from your current branch, this skill uses gh pr create to push local commits, set upstream tracking, and return the PR URL against the default base branch.

What's the best way to automate pushing local commits and opening a pull request?

Automating pushing local commits and opening a pull request is handled by submitting your current working branch to GitHub, which stages your changes for collaborative code review.

Do I need to configure upstream tracking before submitting a pull request?

You do not need to manually configure upstream tracking before submitting a pull request, as the skill ensures proper repository context and handles branch upstream expectations automatically.

Can I use this to open a pull request for a bug fix on a feature branch?

You can use this to open a pull request for a bug fix or feature work on a feature branch, streamlining the workflow from local commit to shared PR URL for team feedback.

Why does creating a pull request require proper repository context?

Creating a pull request requires proper repository context to ensure the gh pr create command targets the correct default base branch and successfully returns the valid PR URL.

What are the limitations of automating pull request creation from a working branch?

Limitations of automating pull request creation include relying on the current working branch already having local commits staged, as it focuses on PR generation and URL return rather than initial branching.