Summarize the Change for Review
Tell Claude to write the PR for the reviewer: what changed, why, and how to test it.
A pull request description is written for the human who has to approve it. When you ask Claude to open a PR, tell it what to include: a summary of what changed, why it changed, and how to test it. Point it at the actual commits or diff so the description reflects reality instead of guesses. A good PR body turns a wall of diff into a decision the reviewer can make quickly.
Where you'll practice this
One Promptles scenario teaches this principle directly.
Open the Pull Request
Your `feature/dark-mode-toggle` branch is pushed and ready. It has three commits: adding a theme context, wiring the toggle UI, and persisting the choice to localStorage. You want Claude Code to open a pull request against `main` with a description that actually helps your…