Generate structured PR descriptions with Summary, What Changed, and risk sections.
npx skills add https://github.com/milistu/agent-skills --skill pr-message
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
Concise and high-signal PR messages help engineers communicate intent, impact, and risk without duplicating information shown on GitHub.
Draft a concise PR message that explains the intent, impact, and risk for your changes.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
Shin0205goAnalyze pull request diffs and generate structured code review comments.
tylerbutlerTrigger Azure DevOps pipelines for Copilot pull requests via GitHub comments.
AutomatticValidate ActivityPub PR branch naming, reviewer assignment, and changelog compliance.
maxenergyRestructure article sections and tighten prose within 240-character paragraphs.
