skills.rest
luohaha
luohahaCOMMUNITY
Explore all skills by this author →
GitHub

pr-description

Generate structured Markdown PR descriptions from Git diffs and commits.

Updated Dec 24, 2025
Search Tags:#git#documentation#code-review#pull-request#pr-description#diff-analysis#change-summary
One-click install
npx skills add https://github.com/luohaha/oh-my-skills --skill pr-description-luohaha
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-description
Source: https://github.com/luohaha/oh-my-skills/tree/main/skills/pr-description
Command: npx skills add https://github.com/luohaha/oh-my-skills --skill pr-description-luohaha

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual PR descriptions are often time-consuming and inconsistent, leaving reviewers with unclear context about why changes were made and what was implemented.

Core Features & Use Cases

  • Generate a structured PR description from diffs, commits, or touched files.
  • Include sections such as Why I'm Doing This and What I'm Doing to convey motivation and implementation details.
  • Support review-focused details like affected modules, risks, and emphasis areas for features, bug fixes, or refactors.

Quick Start

Describe the latest changes by analyzing the current branch diffs or specified files to produce a ready-to-submit PR 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 pull request description from git diffs automatically?▼

You can generate a pull request description from git diffs by analyzing the touched files and commits. The skill outputs a structured Markdown format with clear sections for motivation and implementation details, ready to paste into your PR.

What should a code review summary include for feature branches and bug fixes?▼

A code review summary should include motivation, implementation details, affected modules, and potential risks. Generating structured PR descriptions ensures reviewers understand the context across features, bug fixes, or refactors in your Git workflow.

How do I write a structured PR description for refactoring changes?▼

To write a structured PR description for refactoring changes, summarize the touched files and diff analysis. The resulting Markdown includes structured sections explaining why the refactor is happening and what specific implementation details were changed.

Can I create a ready-to-paste Markdown PR description from commit history?▼

Yes, you can create a ready-to-paste Markdown PR description directly from commit history and diffs. It processes the changes to produce structured sections detailing the motivation and implementation specifics required for effective code reviews.

Does generating PR descriptions from diffs work for all types of Git workflows?▼

Generating PR descriptions from diffs works for standard Git workflows involving features, bugs, or refactors. It analyzes the specified touched files and commits to produce a consistent structured Markdown summary of the changes made.

Related Skills

Explore More Software Engineering Skills→
GeorgeSheppardGeorgeSheppard

update-pr-from-branch

Generate PR titles and descriptions from git branch diffs.

Community
Intermediate
flosrnflosrn

create-pr

Create and push pull requests with auto-generated titles and descriptions.

Community
Intermediate
1024XEngineer1024XEngineer
43

github-pr

Analyze pull request diffs and comments to identify merge risks.

Official
Intermediate
vndkubivndkubi

generate-pr-description

Generate structured pull request descriptions from git diffs and commit history.

Community
Intermediate