skills.rest
accolver
accolverCOMMUNITY
Explore all skills by this author →
Website𝕏@acolveGitHub

pr-description

Generate a structured Markdown PR description from a branch diff.

4|Updated Mar 6, 2026
Search Tags:#documentation#ai-assistant#code-review#structured-output#pull-request#pr-description#branch-diff
One-click install
npx skills add https://github.com/accolver/skill-maker --skill pr-description-accolver
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-description
Source: https://github.com/accolver/skill-maker/tree/main/pr-description
Command: npx skills add https://github.com/accolver/skill-maker --skill pr-description-accolver

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually crafting PR descriptions from branch changes is time-consuming and error-prone; this skill automates the creation of comprehensive, reviewer-friendly PR bodies that explain motivation, scope, and risk.

Core Features & Use Cases

  • Structured PR descriptions including motivation, grouped changes by concept, testing instructions, rollback plan, and reviewer guidance.
  • Works for features, bugfixes, and refactors by deriving context from a branch diff and linked tickets.
  • Enables copy-pasteable, reviewer-ready descriptions that speed up code reviews and approvals.

Quick Start

Provide the branch diff to the skill and it will generate a structured PR description with motivation, changes grouped by concept, testing instructions, rollback plan, and reviewer notes.

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 structured pull request description from a branch diff?▼

A good PR description explains motivation, groups changes by concept, and provides copy-pasteable testing instructions. This ensures reviewers understand the scope and risk, speeding up code reviews and approvals.

Can I automatically group pull request changes by concept instead of by file?▼

You can create reviewer-ready PR descriptions by providing the branch diff and linked tickets. The tool derives context to produce a Markdown body with summary, motivation, changes, testing instructions, rollback plan, and reviewer notes.

Does this tool work for generating PR descriptions for bug fixes and refactors?▼

The generated PR description includes sections for Summary, Motivation, Changes, Testing Instructions, Rollback Plan, and Reviewer Notes. It references related tickets when available to provide complete reviewer guidance.

What is the best way to include testing instructions and a rollback plan in a PR body?▼

The best way to include testing instructions and a rollback plan in a PR body is to generate them from a branch diff. The tool outputs copy-pasteable testing instructions and a rollback plan within the Markdown description.

Related Skills

Explore More Software Engineering Skills→
shopwareLabsshopwareLabs
41

pr-description-writing

Draft conventional commit PR titles and Shopware 5-section descriptions.

Official
Advanced
pantheon-orgpantheon-org
9

pr-comment-resolver

Resolve pull request review comments by fixing source files and replying to threads.

Official
Advanced
cenk1cenk2cenk1cenk2
2

github-pr

Analyze branch commits and diffs to draft GitHub pull request titles and descriptions.

Community
Intermediate
jk278jk278

git-analyzer

Analyze git repositories to summarize commit history and file changes.

Community
Intermediate