pr-description

Generate What/Why/How summaries for GitHub or GitLab PRs with risk assessments.

7|Updated Mar 19, 2026

Search Tags:#git #changelog #pr #risk-assessment #code-review #pull-request

One-click install

npx skills add https://github.com/camilooscargbaptista/cto-toolkit --skill pr-description-camilooscargbaptista

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: pr-description
Source: https://github.com/camilooscargbaptista/cto-toolkit/tree/main/pr-description
Command: npx skills add https://github.com/camilooscargbaptista/cto-toolkit --skill pr-description-camilooscargbaptista

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill removes ambiguity and saves reviewer time by producing concise, senior-level pull request descriptions that explain what changed, why it changed, and what to focus on before a reviewer reads the code.

Core Features & Use Cases

Structured PR templates that produce What / Why / How sections, Changes, Risk Assessment, Review Guide, and Testing checklist tailored to the diff.
Automated analysis of commits, diffs, test and migration files, and PR size to enforce quality gates and suggest splitting or additional checks.
Risk-aware guidance that includes blast radius, rollback plan, and monitoring when high-risk changes or migrations are detected.
Use cases: creating PR descriptions for feature work, bugfixes, refactors, breaking changes, or hotfixes; summarizing branch changes for code reviews; generating review guidance for reviewers.

Quick Start

Use the pr-description skill to generate a What/Why/How PR description that summarizes the branch diff, highlights tests and migrations, and includes a risk assessment.

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 a git diff?▼

To generate a pull request description from a git diff, this skill analyzes your branch commits, file changes, tests, and migrations to automatically produce structured What, Why, and How sections alongside review guidance.

What should a code review guidance section include for high-risk changes?▼

A code review guidance section for high-risk changes should include a risk assessment detailing the blast radius, a rollback plan, and monitoring checks to ensure PR quality gates are satisfied before merging.

Can I automatically summarize branch changes for a GitHub PR?▼

Yes, you can automatically summarize branch changes for a GitHub PR by processing your commit history and repository diffs to extract motivations, identify database migrations, and output reviewer-ready messaging.

Does the generated PR template include a testing checklist?▼

Yes, the generated PR template includes a testing checklist tailored to the specific diff, utilizing automated test detection and PR size analysis to enforce quality gates and suggest additional checks if required.

When should I use an automated PR description generator for code review?▼

You should use an automated PR description generator when preparing GitHub or GitLab messages for feature work, bugfixes, refactors, or hotfixes, ensuring reviewers understand changes before reading the code.