github-pr

Enforce conventional commits and standardized PR descriptions in GitHub workflows.

1|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/wildbitca/ai-resources --skill github-pr-wildbitca
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-pr
Source: https://github.com/wildbitca/ai-resources/tree/main/skills/gpm-curated-github-pr
Command: npx skills add https://github.com/wildbitca/ai-resources --skill github-pr-wildbitca

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Inconsistent PRs and unclear commit messages slow reviews and introduce miscommunication; this Skill enforces conventional commits and clear PR descriptions to standardize and accelerate merging.

Core Features & Use Cases

  • Enforces conventional commits and consistent PR descriptions.
  • Provides templates and examples to guide title, body, and summary content.
  • Use Case: During feature development, generate a clean, well-structured PR that communicates scope and impact to reviewers.

Quick Start

Provide a PR title and body that follow conventional commits guidelines to create a polished pull request.

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 for GitHub pull requests?

You enforce conventional commits for GitHub pull requests by applying standardized templates and validation rules to PR titles, bodies, and commit messages. This ensures consistent communication and accelerates the code review process.

What is the best way to standardize pull request descriptions for code review?

Standardizing pull request descriptions involves using structured templates that guide the title, body, and summary content. This clarifies the scope and impact of changes for reviewers, reducing miscommunication during software development.

Can I use this with the gh CLI to automate pull request creation?

Yes, you can use this with the gh CLI to automate pull request creation. It integrates directly into GitHub PR workflows, including the gh pr create process, to generate polished, convention-compliant pull requests.

Why do inconsistent PR titles and commit messages slow down merging?

Inconsistent PR titles and commit messages slow down merging because they introduce miscommunication and obscure the scope of changes. Enforcing conventional commits and clear descriptions standardizes reviews and accelerates the merge process.

Do I need to provide my own PR template to generate a well-structured pull request?

No, you do not need to provide your own PR template. This Skill provides built-in templates and examples that guide your title, body, and summary content to automatically create a polished, well-structured pull request.