github-pr

Create GitHub Pull Requests with conventional commits via the GitHub CLI.

Updated Mar 8, 2026

Search Tags:#git #code review #pull request #conventional commits #github #cli

Ready to run

npx skills add https://github.com/brivaro/brivaro-ai-wizard --skill github-pr-brivaro

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: github-pr
Source: https://github.com/brivaro/brivaro-ai-wizard/tree/main/skills/github-pr
Command: npx skills add https://github.com/brivaro/brivaro-ai-wizard --skill github-pr-brivaro

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps developers create high-quality GitHub Pull Requests with conventional commit messages and well-structured descriptions, improving code review efficiency and project maintainability.

Core Features & Use Cases

Conventional Commits: Enforces a standard format for commit messages (<type>(<scope>): <short description>).
Structured PR Descriptions: Provides a template for clear and concise PR summaries, change logs, and testing status.
Command-Line Integration: Leverages the GitHub CLI (gh) for seamless PR creation and management.
Use Case: When you've completed a new feature, use this Skill to generate a PR title like feat(auth): implement JWT authentication and a detailed description outlining the changes and testing performed.

Quick Start

Use the github-pr skill to create a pull request with the title 'feat(api): add user endpoint' and a body describing the changes.

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 conventional commit messages?▼

To create a GitHub pull request with conventional commit messages, you can use an automated tool that enforces the `<type>(<scope>): <short description>` format. It leverages the GitHub CLI to generate PR titles like `feat(auth): implement JWT authentication` and structured descriptions.

What's the best way to automate pull request creation via the GitHub CLI?▼

Automating pull request creation via the GitHub CLI is best handled by a script that formats conventional commits and structured descriptions. This allows you to seamlessly generate PRs, manage updates, and set atomic commits directly from your command line.

Does this PR generation method support draft PRs and reviewer assignments?▼

Yes, this PR generation method supports draft PRs and reviewer assignments. It facilitates automated PR management through the GitHub CLI, allowing you to streamline code review workflows by assigning reviewers and applying labels.

How do pull request templates improve code review efficiency?▼

Pull request templates improve code review efficiency by providing a structured format for clear summaries, change logs, and testing status. Using conventional commits alongside these templates ensures maintainable project histories and faster review cycles.

Can I use this GitHub CLI workflow for atomic commits?▼

Yes, you can use this GitHub CLI workflow for atomic commits. The process supports atomic commits and draft PRs, ensuring your code review workflows remain streamlined and your project history stays cleanly segmented.

What is a conventional commit format for a pull request title?▼

A conventional commit format for a pull request title follows the pattern `<type>(<scope>): <short description>`. An example is `feat(api): add user endpoint`, which provides a clear, standardized summary of the changes for better project maintainability.