skills.rest
wesleyosantos91
wesleyosantos91COMMUNITY
Explore all skills by this author →
GitHub

pr-description

Generate structured Pull Request descriptions from git log and git diff.

6|1|Updated Mar 30, 2026
Search Tags:#code review#pull request#breaking changes#release notes#test plan#git diff#pr description
One-click install
npx skills add https://github.com/wesleyosantos91/multi-agents --skill pr-description-wesleyosantos91
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-description
Source: https://github.com/wesleyosantos91/multi-agents/tree/main/devin/.devin/skills/pr-description
Command: npx skills add https://github.com/wesleyosantos91/multi-agents --skill pr-description-wesleyosantos91

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing clear, review-friendly Pull Request descriptions is time-consuming and often inconsistent, which slows down reviews and makes changes harder to understand.

Core Features & Use Cases

  • Commit & Diff Analysis: Summarizes what changed by inspecting commits and the diff/stat across the PR range.
  • Structured Output for Review: Produces a consistent PR description with Summary, Changes, Breaking Changes, Test Plan, and Notes for Reviewers.
  • Practical Review Guidance: Flags when the PR is too large and suggests splitting to keep review manageable.
  • Language Fit: Writes in the same language used by the project (Português ou English).

Quick Start

Generate a structured PR description for my changes using commit history and the diff, following the provided PR template.

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 diff and commit history?▼

To generate a pull request description, the Skill analyzes commit history and file diffs across the target branch range. It extracts changes via git log and git diff, then formats them into a structured Markdown template with summaries and review guidance.

What is the best way to format breaking changes and test plans in a PR description?▼

The best way to format breaking changes and test plans is using a structured Markdown template. This Skill automatically isolates breaking changes and generates a dedicated test plan section from your commit history to ensure review-focused guidance.

Can I analyze large pull requests and get suggestions to split them for code review?▼

Yes, you can analyze large pull requests for code review. The Skill flags oversized PRs during the diff analysis and provides practical suggestions to split the changes into smaller, more manageable review units.

How do I write consistent PR summaries across different project languages like English or Portuguese?▼

To write consistent PR summaries across different languages, the Skill detects the project's language and generates the output accordingly. It supports writing structured change narratives in either English or Português.

Does generating structured PR descriptions require any specific git environment setup?▼

Generating structured PR descriptions requires a standard git environment to access commit history and file diffs. The Skill relies on extracting information via git log and git diff commands, requiring no additional dependencies.

Related Skills

Explore More Product & Management Skills→
paulchiupaulchiu
3

write-pull-request

Generate pull request descriptions from git diff and commit history.

Community
Intermediate
pjcjpjcj
7

create-pr

Create GitHub pull requests with ticket references and Markdown descriptions.

Community
Intermediate
accolveraccolver
4

git-commit-helper

Generate conventional commit messages from staged git changes.

Community
Intermediate
FaysilAlshareefFaysilAlshareef
4

changelog-gen

Generate changelogs from git commits using Conventional Commits and Keep a Changelog formats.

Community
Intermediate