| name | pr-description |
| display_name | PR Description |
| description | Writes clear pull request descriptions from diffs, commits, or implementation notes, including summary, motivation, testing, risks, and rollout. |
| category | git-workflow |
| version | 1.0.0 |
| tags | ["pull-request","git","review","communication","release"] |
| providers | ["claude-code","codex","copilot","openclaw","hermes-agent"] |
| author | agent-skills contributors |
PR Description
Use this skill when preparing or improving a pull request description.
Inputs
- Diff, changed files, commits, branch name, issue links, or implementation notes
- Test results or validation steps
- Any rollout, migration, or risk context
Steps
- Read the diff or change summary and identify the user-facing and technical purpose.
- Separate what changed from why it changed.
- Identify tests run, tests not run, manual checks, and any observed limitations.
- Surface risks, compatibility concerns, migrations, rollout steps, or follow-up work.
- Keep the description concise enough for reviewers to scan.
Output
Provide a PR description with:
- Summary
- Changes
- Testing
- Risks / rollout
- Screenshots or artifacts section when relevant
- Linked issues or follow-ups when known
Guidelines
- Do not overstate test coverage.
- Prefer concrete bullets over marketing language.
- Mention user-visible behavior changes explicitly.
