github-pr

Name: github-pr
Availability: InStock
Author: BreakerOfStems

Create GitHub pull requests with standardized titles and body templates.

Updated Aug 27, 2026

Search Tags:#git #code review #development workflow #pull request #github

Ready to run

npx skills add https://github.com/BreakerOfStems/claude-skills --skill github-pr-breakerofstems

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: github-pr
Source: https://github.com/BreakerOfStems/claude-skills/tree/main/skills/github-pr
Command: npx skills add https://github.com/BreakerOfStems/claude-skills --skill github-pr-breakerofstems

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation of well-documented GitHub pull requests, ensuring consistency and adherence to project standards.

Core Features & Use Cases

Standardized PR Creation: Generates pull requests with predefined title formats and body templates.
Issue Linking: Automatically links pull requests to relevant GitHub issues.
Workflow Guidance: Provides step-by-step instructions for preparing and submitting a PR.
Use Case: When you've completed a feature and linked it to issue #123, use this skill to create a PR with a title like "[#123] Implement user login" and a body that includes a summary, issue link, and testing checklist.

Quick Start

Use the github-pr skill to create a pull request for the current branch, including the issue number 123 in the title and a summary in the body.

Frequently Asked Questions about github-pr

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

FAQPage Schema

How do I create a GitHub pull request with standardized title formats and body templates?▼

To create a GitHub pull request with standardized formats, use this skill to generate predefined title structures and body templates. It enforces consistent naming conventions and includes sections for summaries, issue links, and testing checklists.

How do I automatically link a GitHub pull request to a specific issue?▼

You can automatically link a GitHub pull request to a specific issue by including the issue number in the PR title. This skill enforces issue linking by generating titles like '[#123] Implement user login' to connect PRs to their respective issues.

Do I need the GitHub CLI installed to automate pull request creation?▼

Yes, you need the GitHub CLI (`gh`) installed and authenticated to automate pull request creation. This skill relies on the `gh` command-line tool to execute workflows and submit PRs directly from your development environment.

What is the best way to ensure consistent documentation across feature development and bug fix pull requests?▼

The best way to ensure consistent PR documentation is to enforce body templates and standardized naming conventions. This skill provides workflow guidance for feature development and bug fixes, requiring summaries, issue links, and testing checklists for every submission.

Can I use this pull request workflow for both feature development and code reviews?▼

Yes, you can use this pull request workflow for both feature development and code reviews. It supports multiple use cases by applying standardized templates and issue linking to ensure all code review submissions adhere to project documentation standards.

What should be included in a GitHub pull request body template?▼

A GitHub pull request body template should include a summary of changes, a link to the relevant issue, and a testing checklist. This skill generates these body templates automatically to ensure all necessary documentation is present before submission.