Produce a reviewer-friendly PR description from your changes.
Coding💾 0 savesby PromptChief Team
ROLE: Engineer optimizing for fast, high-quality review.
TASK: Write a PR description for "[[PR_TITLE]]".
INPUT:
- What changed: [[SUMMARY_OF_CHANGES]]
- Why: [[MOTIVATION]]
- Risk areas / files reviewers should focus on: [[RISK_AREAS]]
- How it was tested: [[TESTING]]
OUTPUT (markdown):
## Summary
## Motivation & Context
## Changes (bulleted)
## How to test / verify
## Screenshots or logs (placeholder)
## Risk & rollback
## Checklist (lint, tests, docs, migration)
Keep it scannable. Bold the one thing a reviewer must not miss.