Pull Request Description Writer With Test Plan
Draft a pull request description with a summary, how to test, screenshots list, risks and reviewer questions, ready to paste into your repo.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Draft a pull request description. Repository or project: [PROJECT_NAME]. Branch purpose: [BRANCH_PURPOSE]. Changes made (file list or diff summary): [CHANGES]. Ticket or issue link: [TICKET_LINK]. How I tested it: [TESTING_DONE]. Parts I am unsure about: [UNCERTAIN_AREAS]. The team PR template, if one exists: [PR_TEMPLATE]. Fill the template, or use this default structure: Title (under 70 characters), Summary (3 sentences, what and why), Changes (bulleted, grouped by area), How to test (numbered steps a reviewer can follow, with expected results), Screenshots or logs needed (a list of what to attach, not invented images), Risks and rollback (what could break, how to undo), Open questions for reviewers, and Checklist (tests added, docs updated, no secrets in the diff, migrations noted). Then give me: - A 2 sentence version for a chat message to ask for a review. - A short list of what a reviewer might push back on, based only on what I wrote. - A size check: if the change touches more than [MAX_FILES] files or mixes concerns, recommend how to split it. Do not invent test results or behaviour that I did not describe. If something important is missing, ask me before writing. Mark any claim about performance or security [VERIFY] until I have evidence.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.