pr Prompt
You are an expert developer writing a Pull-Request description for code reviewers. ############################## ## INPUT DATA ## ############################## <<<DIFF>>> {{ diff }} <<<END DIFF>>> {{#if tree}} <<<FILE_TREE>>> {{ tree }} <<<END FILE_TREE>>> {{/if}} Branch : {{ branch }} Target : {{ target }} {{#if commits}} <<<COMMITS>>> {{ commits }} <<<END COMMITS>>> {{/if}} ############################## ## TASK ## ############################## Generate **one** PR draft that: 1. Starts with a concise **title** following `<type>(optional-scope): <description>` where **type** ∈ `feat | fix | docs | style | refactor | perf | test | build | ci | chore`. 2. Provides a **body** in Markdown with these sections *(omit a section if empty)* - **Overview** – why the change is needed (≤ 2 sentences). - **Key Changes** – bullet list of the most important code areas / commits. - **Implementation Notes** – notable design decisions. - **Migration / Checklist** – steps for users or follow-ups (optional). Constraints - Keep the title ≤ 60 characters, imperative mood (“add X”, not “added X”). - Summarise; do **not** dump the entire diff again. ############################## ## OUTPUT ONLY ## ############################## Return **exactly** one JSON object **without** markdown fences or extra text: { "title": "<generated-title>", "body": "<markdown-body>" }
fill the variables
This prompt has 9 variables. Pro fills them into a ready-to-paste prompt for you — no manual find-and-replace.
{{ diff}{{#if tree}{{ tree}{{/if}{{ branch}{{ target}{{#if commits}{{ commits}{"title": "<generated-title>",
"body": "<markdown-body>"}
Unlock with Pro →when to use it
Community prompt sourced from the open-source GitHub repo keli-wen/gitai-cli (MIT). A "pr Prompt" style prompt — adapt the placeholders and specifics to your task. Imported as-is and not independently retested here, so check the output before relying on it.
tags
codingcommunitydeveloper
source
keli-wen/gitai-cli · MIT
more in Coding
Coding✓ tested
Senior code review (strict mode)
senior staff engineer running a merciless but fair review
Coding✓ tested
Debug by hypothesis, not by guessing
debugging partner who forms theories before touching code
Coding✓ tested
Generate tests from described behavior
test engineer who writes tests that would actually catch regressions