pr-description

Generates plain-language summaries and structured sections for pull request descriptions.

12|2|Updated Jan 2, 2026

Search Tags:#documentation #writing #collaboration #review #pr #description #pull-request

Ready to run

npx skills add https://github.com/osolmaz/tools --skill pr-description-osolmaz

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PR descriptions are often unclear or incomplete, making reviews slower. This skill generates a plain, reviewer-friendly summary at the top and follows with structured sections that explain the change and its rationale.

Core Features & Use Cases

Plain top summary: presents the problem, changes, and rationale in plain language.
Structured sections: includes details and explanations that help reviewers understand implementation choices.
Use Case: open a PR or request an improved description for an existing PR to speed up reviews and onboarding.

Quick Start

Provide a short summary of the change and ask the skill to generate a 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 write a clear pull request description for code review?▼

To write a clear pull request description, provide a short summary of the code changes and generate a plain-language top summary with structured technical sections explaining the problem, changes, and rationale for reviewers.

What should be included in a PR description to help reviewers?▼

A helpful PR description includes a plain-language top summary of the problem and changes, plus structured technical sections detailing the implementation rationale to assist reviewers and future readers.

Can I generate an improved description for an existing pull request?▼

Yes, you can improve an existing pull request description by providing a short summary of the change to generate a clearer, structured explanation of the problem, changes, and rationale for reviewers.

What is the best way to structure PR documentation for future readers?▼

The best way to structure PR documentation is to provide a plain-language summary at the top, followed by structured technical sections explaining the change and rationale, ensuring future readers understand implementation choices.

Why are my pull request descriptions causing slow code reviews?▼

Pull request descriptions cause slow code reviews when they are unclear or incomplete. Generating a reviewer-friendly summary with structured sections explaining the change and rationale speeds up the review and onboarding process.