skills.rest
hackberrybay
hackberrybayOFFICIAL
Explore all skills by this author →
WebsiteGitHub

pr-description

Generate a structured PR title and description from branch diffs.

1|Updated Apr 8, 2026
Search Tags:#git#diff#generate#code-review#pull-request#commit-messages#pr-description
One-click install
npx skills add https://github.com/hackberrybay/hb-code-reviewer --skill pr-description-hackberrybay
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-description
Source: https://github.com/hackberrybay/hb-code-reviewer/tree/main/skills/pr-description
Command: npx skills add https://github.com/hackberrybay/hb-code-reviewer --skill pr-description-hackberrybay

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This tool generates a concise, ready-to-paste PR title and description from the current branch diff by analyzing commit messages and changed files to streamline PR creation.

Core Features & Use Cases

  • Reads commit messages and file changes to craft a clear PR title and a descriptive body.
  • Produces a structured PR description with What/How/Testing sections suitable for GitHub.
  • Helps speed up PR creation on feature branches, bug fixes, or multi-commit PRs.

Quick Start

Run the pr-description command after making changes to automatically generate a ready-to-paste PR title and description.

Frequently Asked Questions about pr-description

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

FAQPage Schema
How do I generate a PR description from a git diff automatically?▼

To generate a PR description from a git diff, you run the pr-description command after making changes. It analyzes commit messages and changed files to produce a ready-to-paste PR title and description.

What is the best way to write a structured pull request description for code review?▼

The best way to write a structured pull request description is using an automated generator that reads your branch diff. It outputs a ready-to-paste PR body with concise What, How, and Testing sections.

Can I use commit messages to create a PR title for feature branches?▼

Yes, you can use commit messages to create a PR title for feature branches. The generator reads your commit history and file changes to craft a clear, structured PR title and descriptive body.

Does the generated PR description work with GitHub code review workflows?▼

Yes, the generated PR description works with GitHub code review workflows. It produces a ready-to-paste description with a concise title and What/How/Testing sections suitable for GitHub and similar platforms.

What do I need to generate a PR title from a branch diff?▼

You need the git history context and the current branch diff to generate a PR title. The tool requires no additional dependencies to analyze changes and produce a structured pull request description.

How to handle multi-commit PR description generation for bug fixes?▼

To handle multi-commit PR description generation for bug fixes, run the pr-description command. It analyzes all commit messages and changed files on the branch to output a unified, structured PR description.

Related Skills

Explore More Software Engineering Skills→
alirezarezvanialirezarezvani
763

git-commit-helper

Generate conventional commit messages from staged git diff changes.

Community
Basic
assertchrisassertchris
2

custom-submit-pr

Create a GitHub pull request with the gh CLI and assign it to assertchris.

Community
Intermediate
ebinnionebinnion
5

testing-plan-from-history

Analyze git history and PRs to generate testing instructions for changed files.

Community
Intermediate
JsplixJsplix

code-review-pr-body

Generate structured pull request body drafts from git diffs.

Community
Intermediate