pr

Create formatted pull requests from Git branches using gh pr create.

Updated Feb 10, 2026
One-click install
npx skills add https://github.com/mjbellantoni/scm-tools-claude --skill pr-mjbellantoni
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr
Source: https://github.com/mjbellantoni/scm-tools-claude/tree/main/skills/pr
Command: npx skills add https://github.com/mjbellantoni/scm-tools-claude --skill pr-mjbellantoni

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the process of creating pull requests, ensuring they adhere to project-specific formatting standards for titles and bodies, which is crucial for maintainable Git history and efficient code reviews.

Core Features & Use Cases

  • Automated PR Creation: Generates pull requests directly from your current branch.
  • Standardized Formatting: Enforces strict rules for PR titles (imperative mood, character limits) and bodies (summary, test plan).
  • Use Case: After completing a feature, use this Skill to create a well-formatted pull request that clearly communicates the changes and how to test them, facilitating faster reviews and merges.

Quick Start

Use the pr skill to create a pull request for the current branch.

Frequently Asked Questions about pr

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

FAQPage Schema
How do I create a formatted pull request in GitHub from my current branch?

To create a formatted pull request, you can use the pr skill to automate the `gh pr create` command for your current Git branch. It generates a PR with a standardized title and a body containing a summary and test plan.

How do I enforce commit message standards for pull request titles?

Enforcing commit message standards for pull request titles is handled automatically by the pr skill. It checks that your PR title uses imperative mood and adheres to character limits to ensure maintainable Git history.

Can I automate adding a summary and test plan to my GitHub pull request body?

Yes, you can automate adding a summary and test plan to your GitHub pull request body using the pr skill. It structures the PR body to clearly communicate changes and testing steps for efficient code reviews.

What is the best way to standardize pull request formatting across development workflows?

The best way to standardize pull request formatting across development workflows is to use an automated tool like the pr skill. It enforces strict title rules and body structures directly from your Git branch.

Do I need the GitHub CLI to create standardized pull requests from a Git branch?

Yes, you need the GitHub CLI installed because the pr skill utilizes the `gh pr create` command to automate the pull request creation process from your current Git branch.

Why does my pull request creation fail to meet code review formatting standards?

Your pull request creation may fail code review standards if the title lacks imperative mood or the body misses a summary and test plan. The pr skill enforces these formatting rules automatically to prevent such issues.