Write a pull request description reviewers can act on
A title, a summary of what moved, where to look first, and how to verify it — written for someone who has not opened the diff.
Send what changed and why. The Agent writes the description a reviewer reads first, so they arrive at the diff knowing what moved, why, and which part needs their attention.
Good for
A developer with a pull request waiting on team review.
Not for
Reviewing the diff itself.
What you give
- What changed
- Why it changed
- Kind of change
- What reviewers should know (optional)
What you get back
- 1. Title
- 2. Summary of the change
- 3. Why
- 4. Where to look first
- 5. How to verify
- 6. Risk and rollback
Example
See an example
## Title fix(auth): send expired sessions back to the login screen ## Summary of the change Drops the silent retry path when a session refresh returns 401. The expired session is cleared and the browser goes to the login screen with the original address attached as returnTo. ## Why An expired session left the screen frozen with no explanation until the user reloaded. ## Where to look first 1. Whether the session is cleared before the redirect, in that order. 2. Whether returnTo can be made to hold an external address. ## How to verify Clear the session cookie, open a protected screen, and confirm it redirects to login and comes back to the original screen after signing in. ## Risk and rollback On flaky networks a transient refresh failure now sends the user to login more often. Reverting this single commit restores the previous retry behavior.
Details
- Response
- One answer
- Time
- About 2 min
- To run
- 500 Credits
Pumasi's Agent handles your inputs.