pr

Generate Conventional Commits-compliant PR titles and descriptions from branch commits.

7|Updated Nov 30, 2019
One-click install
npx skills add https://github.com/dstanberry/dotfiles --skill pr-dstanberry
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr
Source: https://github.com/dstanberry/dotfiles/tree/main/ai/claude/skills/pr
Command: npx skills add https://github.com/dstanberry/dotfiles --skill pr-dstanberry

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Drafting consistent PR titles and descriptions from branch commits is time-consuming and error-prone; this skill automates that process.

Core Features & Use Cases

  • Auto-generate a Conventional Commits-compliant PR title from the branch commits.
  • Produce a concise, reviewer-friendly PR description that highlights scope and rationale.
  • Create a new PR or update an existing one via gh pr create or gh pr edit based on the current branch history.

Quick Start

Provide the current branch context to generate or update a PR title and description.

Frequently Asked Questions about pr

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

FAQPage Schema
How do I auto-generate a PR title and description from branch commits?

You can auto-generate a PR title and description by analyzing your branch commits to derive a Conventional Commits-compliant title and compile a concise summary of recent changes for your pull request.

Can I update an existing PR description when new commits arrive?

Yes, you can update an existing PR description when new commits arrive by applying the generated title and compiled description to the current branch history via the gh pr edit command.

Does the auto-generated PR title follow Conventional Commits standards?

Yes, the auto-generated PR title strictly follows the Conventional Commits discipline, deriving the title directly from the branch commits to ensure consistent formatting and clear scope.

What is the best way to prepare a pull request description for gh pr create?

The best way to prepare a pull request description for gh pr create is to automatically compile a concise, reviewer-friendly summary from your branch commits that highlights the scope and rationale of recent changes.

How do I create a new pull request using auto-generated descriptions?

You create a new pull request by generating a coherent title and description from your branch commits, then applying that compiled text directly through the gh pr create command for the feature branch.

Are there limitations when generating PR descriptions from branch commits?

Generating PR descriptions from branch commits relies on the quality of your commit history; if commits lack clear scope and rationale, the resulting reviewer-friendly description may not accurately reflect recent changes.