github-pr

Automate GitHub PR creation with conventional commits and structured descriptions.

618|89|Updated Jan 16, 2026
One-click install
npx skills add https://github.com/Gentleman-Programming/Gentleman-Skills --skill github-pr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-pr
Source: https://github.com/Gentleman-Programming/Gentleman-Skills/tree/main/curated/github-pr
Command: npx skills add https://github.com/Gentleman-Programming/Gentleman-Skills --skill github-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams produce consistent, high-quality pull requests by enforcing conventional commits and generating clear, structured PR descriptions. It reduces review time and miscommunication by standardizing messaging across PRs.

Core Features & Use Cases

  • Conventional commits enforcement: ensures PR titles follow the conventional-commit format (feat, fix, docs, etc.).
  • Standard PR descriptions: auto-generates or validates a structured PR body with Summary, Changes, and References.
  • Wide applicability: suitable for individual contributors and large projects using gh CLI to manage PRs across repositories.

Use Case

A maintainer wants every PR to follow a strict message pattern and a consistent description when merging feature work or bug fixes. This Skill can be invoked during PR creation to automatically format the title and body, ensuring compliance and readability.

Quick Start

gh pr create --title "feat(auth): add OAuth2 login" --body "## Summary

  • Implemented OAuth2 login flow
  • Updated authentication middleware
  • Closes #123"

Frequently Asked Questions about github-pr

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

FAQPage Schema
How do I enforce conventional commits in pull requests?

Conventional commits standardize PR titles using prefixes like feat, fix, docs to categorize changes. This Skill automates PR creation with conventional commit formatting, ensuring titles follow the pattern and descriptions include structured sections for summary, changes, and references.

What's the best way to standardize pull request descriptions across a team?

Standardized PR descriptions reduce review time by providing consistent structure. This Skill generates structured PR bodies with Summary, Changes, and References sections, enforcing the same template across all PRs created via gh CLI commands.

Can I automate PR creation with gh CLI to follow a consistent format?

Yes. This Skill automates PR creation using gh pr commands, applying conventional commit types to titles and generating structured description templates automatically, eliminating manual formatting for every pull request.

How do conventional commits improve code review workflow?

Conventional commits provide clear categorization of changes—feat, fix, docs, etc.—making PR intent immediately visible. Combined with structured descriptions, reviewers quickly understand scope and impact, reducing miscommunication and review cycles.

Does this work with existing GitHub repositories and multiple projects?

Yes. The Skill applies across repositories using gh CLI, suitable for individual contributors and large projects managing multiple codebases. It enforces the same conventional commit and description standards regardless of repository or team size.

What happens if a PR title doesn't follow conventional commit format?

This Skill enforces conventional commit types during PR creation, validating or auto-generating titles in the required format. It prevents non-compliant titles by applying the standardized pattern automatically through gh pr commands.