pr-description

name	pr-description
description	Use when opening a pull request, or when asked to write or improve a pull request description. Produces a plain summary up top, then structured technical sections with paired plain-language explanations.

PR Description

Use this skill when writing a PR description.

When this skill is invoked, write a PR description that helps both reviewers and future readers.

The top summary must answer this question:

what the hell is this about?

That means the summary should:

• lead with the real user-facing or developer-facing problem
• say what changed in simple words
• say why the PR matters
• include the relevant context needed to understand the PR
• include the main steps taken to implement the change
• use short full sentences
• avoid jargon unless it is required
• stand on its own without the rest of the PR
• state that context and those implementation steps plainly

Write the top summary in the same style as the amk skill:

• short full sentences
• main point first
• concrete words
• no meta lead-ins
• no unnecessary bullets
• usually 2 to 4 sentences
• put each sentence on its own line

After the summary, use these sections by default unless the user asks for a different shape.

In every section, start with plain full sentences first. Do that before any bullets, commands, or technical detail. Do not create separate sections called Plain Language.

---

Summary

• Plain first.
• This is the "what is this about?" section.
• Do not hide the main point behind implementation details.

What Changed

• Start with 1 to 3 plain sentences.