← Prompt Library / Engineering
Write a PR description that gets thorough review fast: what changed, why, how to test it, and where the reviewer should look hardest.
Write the PR description for this change: {{change_summary}} (the diff or a summary of what I did and why).
Format: What & Why (2-3 sentences — the problem, not just the mechanics), Changes (bulleted, grouped by area), How to test (exact steps a reviewer can follow), Where to look hardest (the risky or clever part — pointing reviewers at danger is a strength), Screenshots/before-after if UI, and Out of scope (what I deliberately didn't do, so review doesn't relitigate it). Keep it honest: if a change is a hack with a reason, say so and link the follow-up.
Fields like {{ this }} are placeholders — replace them with your own details, or let Aria ask you for them.
This prompt runs with Aria connected to your email, files, CRM and 40+ other services — and you can schedule it to run automatically.
Start Free WeekReview a diff for correctness, security, and readability issues.
Get a plain-English walkthrough of unfamiliar code.
Generate thorough unit tests for a function.
Diagnose an error systematically: likely causes ranked with reasoning, the cheapest test for each, a...
Build a regular expression from a plain-English requirement — explained token by token, tested again...
Turn a plain-English data question into a working SQL query — with the assumptions stated, a readabl...