github-pr

Generate GitHub Pull Requests with conventional titles and structured descriptions via gh CLI.

19|2|Updated Apr 28, 2026
One-click install
npx skills add https://github.com/CamiloAndresGTRUniandes/lucy-ai --skill github-pr-camiloandresgtruniandes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-pr
Source: https://github.com/CamiloAndresGTRUniandes/lucy-ai/tree/main/skills/github-pr
Command: npx skills add https://github.com/CamiloAndresGTRUniandes/lucy-ai --skill github-pr-camiloandresgtruniandes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of unclear, inconsistent Pull Request titles and descriptions by enforcing conventional commit formatting and a structured PR body that reviewers can quickly assess.

Core Features & Use Cases

  • Conventional PR titles: Generates or validates PR titles using a consistent <type>(<scope>): <description> convention to improve searchability and release hygiene.
  • Reviewer-ready PR descriptions: Guides authors to write a structured body with Summary, Changes, Testing, and issue closing keywords (e.g., Closes #123).
  • PR creation via GitHub CLI: Helps you draft, label, assign reviewers, and preview PR outcomes using gh pr create.

Use case example: You’ve implemented an authentication fix and want a PR that clearly explains what changed, why it matters, what you tested, and how it relates to an existing issue—without writing the same review boilerplate every time.

Quick Start

Ask the assistant to create a draft PR using gh CLI with the title formatted as a conventional commit and a description that includes Summary, Changes, Testing checkboxes, and a Closes reference.

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 titles?

To create a GitHub pull request with conventional commit titles, format your title as `<type>(<scope>): <description>`. This enforces consistency, improves repository searchability, and maintains clear release hygiene for your project.

What should be included in a structured PR description for code review?

A structured PR description for code review should include Summary, Changes, and Testing sections. It should also contain optional issue-closing keywords, such as `Closes #123`, to link and automatically close related GitHub issues upon merging.

How do I use GitHub CLI to open a draft PR with labels and reviewers?

Use GitHub CLI to open a draft PR by executing `gh pr create` with appropriate flags for drafts, labels, and reviewer assignments. This allows you to preview PR outcomes and assign reviewers directly from the command line.

Why use conventional commits for pull request titles?

Conventional commits for pull request titles solve the problem of unclear, inconsistent PR naming. By applying a standardized format, reviewers can quickly assess the purpose of changes, improving overall searchability and release tracking.

Does this PR creation approach work with existing GitHub issues?

Yes, this PR creation approach works with existing GitHub issues by using issue-closing keywords like `Closes #123` within the structured description. This links the pull request to the issue and closes it automatically upon merging.