skills.rest
theomonfort
theomonfortCOMMUNITY
Explore all skills by this author →
Website𝕏@theomonfort_GitHub

describe-pr

Generate structured pull request descriptions from GitHub diffs and commits.

3|Updated Feb 20, 2026
Search Tags:#code review#pull request#github#diff#pr description#describe-pr
One-click install
npx skills add https://github.com/theomonfort/theomonfort --skill describe-pr-theomonfort
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: describe-pr
Source: https://github.com/theomonfort/theomonfort/tree/main/.github/skills/describe-pr
Command: npx skills add https://github.com/theomonfort/theomonfort --skill describe-pr-theomonfort

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PR descriptions are often terse or incomplete, making reviews harder to understand and slowing down merging.

Core Features & Use Cases

  • Analyze code changes and diffs to summarize impact and rationale.
  • Gather PR metadata and commit history to provide context for reviewers.
  • Generate a structured, review-ready PR description suitable for small or large changes.

Quick Start

Provide a detailed, structured PR summary by analyzing the current diff, PR metadata, and commit history.

Frequently Asked Questions about describe-pr

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

FAQPage Schema
How do I generate a comprehensive PR description from a GitHub diff?▼

A comprehensive PR description summarizes code changes, impact, and rationale by analyzing the diff and commit history. It uses gh CLI to fetch PR metadata, producing a structured, review-ready narrative that helps reviewers understand changes quickly.

What's the best way to automate pull request summaries for multi-branch collaboration?▼

The best way to automate pull request summaries is to gather PR metadata and commit history to provide context for reviewers. Analyzing code changes across multi-branch collaboration generates a structured, review-ready description automatically.

Can I use the gh CLI to fetch commits and diffs for a code review?▼

Yes, you can use the gh CLI to fetch commits and diffs for a code review. The tool gathers PR metadata, commits, and diffs via the CLI to produce a structured, review-ready pull request description suitable for small or large changes.

Why are detailed PR descriptions needed for merging code changes?▼

Detailed PR descriptions are needed because terse or incomplete descriptions make code reviews harder to understand and slow down merging. Generating a comprehensive narrative with PR metadata provides necessary context for reviewers.

Does this PR description generator work with large code changes?▼

Yes, this PR description generator works with large code changes. It analyzes diffs and commit history to summarize impact, generating a structured, review-ready PR description suitable for both small and large modifications.

Related Skills

Explore More Software Engineering Skills→
SuniljitSuniljit

pr-review

Fetch pull request metadata and diffs to generate a structured review.

Community
Intermediate
Monjyu1101Monjyu1101
1

github-pr-workflow

Automate GitHub PR lifecycle from branch creation through CI checks to merge.

Community
Advanced
mpetitompetito

pr-management

Manage GitHub pull request review threads, comments, and branch merges.

Community
Intermediate
StudyDriftStudyDrift
58

make-pr-easy-to-review

Clean noisy PR history and add reviewer guidance without altering code behavior.

Official
Intermediate