Pull Request Description Writer
Get a task-specific pull request description writer workflow with relevant variables, grounded analysis, an organized deliverable, and verification guidance...
Prompt
Turn the supplied inputs into **pull request description writer**. Optimize for the person searching “pull request description writer prompt”: they need a clear result, the reasoning that affects it, and an obvious next step. ## Situation to solve — Pull Request Description Writer - [ACTUAL_BEHAVIOR] — for Pull Request Description Writer, supply the relevant actual behavior. If unavailable, label [ACTUAL_BEHAVIOR] `unknown`; never infer it. - [CONSTRAINTS] — for Pull Request Description Writer, supply the relevant constraints. If unavailable, label [CONSTRAINTS] `unknown`; never infer it. - [LANGUAGE] — for Pull Request Description Writer, supply the relevant language. If unavailable, label [LANGUAGE] `unknown`; never infer it. - [EXPECTED_BEHAVIOR] — for Pull Request Description Writer, supply the relevant expected behavior. If unavailable, label [EXPECTED_BEHAVIOR] `unknown`; never infer it. - [REPRODUCTION_STEPS] — for Pull Request Description Writer, supply the relevant reproduction steps. If unavailable, label [REPRODUCTION_STEPS] `unknown`; never infer it. - [CODE] — for Pull Request Description Writer, supply the relevant code. If unavailable, label [CODE] `unknown`; never infer it. - [REQUIRED_POINTS] — for Pull Request Description Writer, supply the relevant required points. If unavailable, label [REQUIRED_POINTS] `unknown`; never infer it. ## How to work — Pull Request Description Writer 1. Draft only after locking the audience, purpose, facts, voice, and desired action. 2. Deliver a publishable version plus a compact rationale for important choices. 3. Identify the smallest causal code path. 4. Separate confirmed behavior from hypotheses. 5. Consider edge cases, security, and backward compatibility. 6. Show a minimal change before optional refactoring. 7. Boundary for Pull Request Description Writer: Do not invent APIs, packages, files, runtime behavior, command output, or successful test results. ## Make the answer usable — Pull Request Description Writer - **Technical finding for Pull Request Description Writer** — pull request description writer prompt evidence → Pull Request Description Writer; omit preamble. - **Evidence or reproduction for Pull Request Description Writer** — material inputs for Pull Request Description Writer, each connected to pull request description writer prompt. - **Minimal change for Pull Request Description Writer** — ready-to-use Pull Request Description Writer, formatted for pull request description writer prompt. - **Test coverage for Pull Request Description Writer** — Pull Request Description Writer weak points, unknowns, and pull request description writer prompt limits. - **Verification command for Pull Request Description Writer** — pull request description writer prompt → verify Pull Request Description Writer before use. ## Integrity check — Pull Request Description Writer Before returning the Pull Request Description Writer, remove filler, label every unresolved fact, and verify that each recommendation connects to a supplied goal.
How to use this prompt
Replace only the bracketed fields relevant to your situation. Keep unknown information marked as unknown, paste the completed prompt into a capable AI assistant, and review the result before using it.
Best AI model
ChatGPT • Gemini • capable reasoning assistants
