pr

Rebase a branch onto a target base and create a GitHub Pull Request.

8|1|Updated Mar 1, 2026
One-click install
npx skills add https://github.com/JoeCP17/LLM-Dot-files --skill pr-joecp17
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr
Source: https://github.com/JoeCP17/LLM-Dot-files/tree/main/claude/skills/pr
Command: npx skills add https://github.com/JoeCP17/LLM-Dot-files --skill pr-joecp17

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the hassle of preparing a branch for review by rebasing onto the correct base branch, auditing the full commit history, and opening a properly described GitHub Pull Request.

Core Features & Use Cases

  • Rebase workflow: Rebases the current branch onto the chosen base branch to keep the PR diff clean and linear.
  • Commit-history analysis: Reviews the full commit range and produces an accurate PR Summary and Changes section that reflect everything in the branch.
  • Safe push and PR creation: Pushes with history-rewrite safety and creates the PR via GitHub CLI with a title/body that follow practical rules.

Quick Start

Ask to open a PR (for example, “/pr main”) and let the Skill rebase your branch onto the specified base branch, push it, and create the GitHub Pull Request with a complete summary.

Frequently Asked Questions about pr

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

FAQPage Schema
How do I open a GitHub PR with a rebased branch and clean commit history?

To open a GitHub PR, this process rebases your current branch onto a target base branch, analyzes the full commit history for accurate descriptions, pushes with force-with-lease, and creates the pull request via gh cli.

What is the best way to rebase my branch onto a target base branch before creating a pull request?

Rebasing your branch onto a target base branch keeps the PR diff clean and linear. This workflow automatically determines the base branch, rewrites the commit history, and pushes safely using force-with-lease.

How does commit-history analysis work when generating a GitHub pull request?

Commit-history analysis reviews the full commit range on your branch to produce an accurate PR Summary and Changes section. This ensures the GitHub pull request body reflects all actual modifications made.

What happens if I have uncommitted changes or rebase conflicts when opening a PR?

If uncommitted changes or rebase conflicts exist, the PR creation process stops immediately. You must resolve these git rebase conflicts and commit changes before retrying the branch workflow.

Do I need the gh cli installed to automate GitHub pull request creation from my branch workflow?

Yes, you need the gh cli installed because the PR creation step executes directly through GitHub CLI commands to push your rebased branch and submit the compliant title and body.

Can I specify a custom base branch when I ask to open a GitHub PR?

Yes, you can specify a custom base branch explicitly, such as requesting to open a PR onto main. If no base branch is provided, it defaults to the origin branch for the rebase workflow.