# describe-pr (Unified Skill)

## Core Instructions (SKILL.md)

# Generate PR Description

Create a pull request description based on the actual PR changes.

## Procedure

1. Identify the PR.
2. Gather diff, commit history, and metadata.
3. Analyze what changed, why it changed, and reviewer-relevant impact.
4. Generate the description using `references/pr-template.md`.
5. Show the draft to the user before updating the PR.

## Rules

- Focus on why, not just what.
- Be specific about impact, testing, and reviewer guidance.
- Highlight breaking changes, security implications, and rollout concerns when present.


---

## Reference: pr-template.md

```markdown
## Summary

[2-3 sentence overview of what the PR does and why]

## Changes

Key changes:
- [Specific change with rationale]
- [Specific change with rationale]

Files changed:
- `path/to/file.ext` - [What changed and why]

## Motivation

[Problem solved or requirement fulfilled]

## Implementation Details

[Key decisions and tradeoffs]

## Related

- Issue: [reference if applicable]
- Plan: `plans/...` [if applicable]
- Design doc: `docs/...` [if applicable]
- Depends on: [PR or issue]
- Blocks: [PR or issue]

## Testing

Automated:
- [ ] [Command or suite]

Manual:
- [ ] [Verification step]

## Breaking Changes

[List them, or state none]

## Security Considerations

[List them, or state none]

## Performance Impact

[List them, or state none]

## Rollout Plan

[If needed]

## Follow-up Work

- [ ] [Follow-up]

## Reviewer Notes

[What reviewers should focus on]
```


---