pr-message

Generate structured PR descriptions with Summary, What Changed, and risk sections.

7|Updated Feb 2, 2026

Search Tags:#workflow #documentation #markdown #communication #pr #code-review #pull-request

Ready to run

npx skills add https://github.com/milistu/agent-skills --skill pr-message

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pr-message
Source: https://github.com/milistu/agent-skills/tree/main/skills/pr-message
Command: npx skills add https://github.com/milistu/agent-skills --skill pr-message

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Concise and high-signal PR messages help engineers communicate intent, impact, and risk without duplicating information shown on GitHub.

Core Features & Use Cases

Structured PR descriptions with sections like Summary, What Changed, Testing, Screenshots, Risk / Rollout, and Notes for Reviewers.
Enforces guidance to avoid duplicating information visible on GitHub and to keep the message scannable.
Use cases include opening PRs for feature work, bug fixes, or refactors where clear context is required.

Quick Start

Draft a concise PR message that explains the intent, impact, and risk for your changes.

Frequently Asked Questions about pr-message

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

FAQPage Schema

How do I write a concise pull request description for code review?▼

To write a high-signal PR description, use structured sections like Summary, What Changed, Testing, and Risk/Rollout. This format enforces one to three sentences for the summary and one to three bullets for changes, ensuring reviewers quickly grasp intent and impact without wading through duplicated GitHub data.

What should be included in a PR message to guide reviewers effectively?▼

A PR message to guide reviewers should include Summary, What Changed, Testing, Screenshots, Risk/Rollout, and Notes for Reviewers. This structure clarifies behavior, summarizes changes, and explicitly highlights risks, ensuring reviewers understand the context without duplicating information already visible on GitHub.

How do I structure a PR message for a major feature or refactor?▼

Structure a PR message for a major feature or refactor by applying a strict template with Summary, What Changed, and Testing sections. This enforces concise communication of one to three sentences or bullets, preventing information overload and clarifying the specific intent, impact, and risk of the refactor.

How do I avoid duplicating visible GitHub data in my pull request descriptions?▼

Avoid duplicating visible GitHub data by focusing your PR descriptions on intent, impact, and risk instead of listing commit history. The format enforces a scannable structure with dedicated sections like Summary and What Changed, pushing you to provide high-signal context that the GitHub UI does not already show.

Does this PR description format work for bug fixes and refactoring tasks?▼

Yes, this PR description format works for bug fixes and refactoring tasks. It is explicitly designed for opening PRs across code, refactor, or feature work, using sections like Summary, Testing, and Notes for Reviewers to clarify behavior and guide reviewers through any type of code modification.