Free browser utility
All toolspull request template generator
Prepare a pull request for human review. Keep the reason for the change, linked work, commands to run and reported acceptance evidence separate, with unchecked review tasks and explicit gaps.
This utility generates in your browser without uploading input. No signup or AI provider is needed. Use non-secret project context.
Generated pull request template
Start with the example or enter your own facts. Use Generate PR template when you are ready, then review the result.
Methodology and format
This generator builds a review document for a proposed change, rather than a coding-session handoff. It places your change area, purpose, linked work, verification commands, risk notes and acceptance evidence under separate Markdown headings. Only change area is required; missing optional answers become visible placeholders.
Commands are plans to verify, not execution results. Evidence is labeled reported and unverified. Four review tasks always start unchecked, and a separate placeholder asks for actual results and remaining gaps. The utility never confirms test success, deployment, approval or readiness to merge.
For a reusable GitHub template, edit out change-specific facts and save pull_request_template.md at the repository root, in docs/, or in .github/. GitHub makes templates available from the default branch. Multiple templates belong in a PULL_REQUEST_TEMPLATE/ subdirectory of one of those locations and are selected with GitHub's template query parameter. The GitHub source below documents these locations; this utility does not write to your repository.
Input is treated as plain facts: surrounding whitespace is trimmed, while internal text is preserved inside fenced Markdown blocks. The fence expands around supplied backticks, so user headings, HTML or checked boxes cannot become template structure. References inside these blocks are literal text; edit them into Markdown links yourself when appropriate. GitHub's task list documentation below defines the unchecked checkbox syntax used for the review tasks.
Limits are 500 UTF-16 code units for change area; 2,000 each for purpose, linked work and risk notes; and 3,000 each for verification commands and acceptance evidence. The shared form rejects non-text or oversized values and restores only known fields from supported share links. Share URLs are limited to 8,000 characters; export larger drafts as Markdown. Malformed links produce an error without replacing your current input.
Generation runs in your browser without uploading input or calling an AI provider. The utility does not automatically store drafts or log their contents. Copy, export and sharing require your action. Copy share link puts input in the URL fragment, readable by anyone with the link. Use non-secret facts; this utility description does not describe every website request or script.
GitHub: creating a pull request template — Official supported repository locations, default-branch availability and multiple-template selection. Reviewed October 9, 2026.
GitHub: Markdown task lists — Unchecked Markdown tasks use a hyphen and empty brackets. This output uses ordinary task lists, not retired tasklist blocks. Reviewed October 9, 2026.
Limitations
The utility cannot inspect your diff, execute commands, open references, validate acceptance evidence or assess risk. A filled form is not proof of correctness. Review the actual change and record real results before requesting approval.
The output is valid Markdown with a suggested review structure, not a GitHub policy or merge gate. Repository owners choose their own required checks. No security, accessibility or deployment checks are inferred from the supplied change area.
The example is fictional. Replace its facts before use. For a reusable repository template, replace all change-specific facts with prompts; for a single PR, fill the results and gap placeholders after verification. Exported files and shared links are not secure channels for confidential information.
Frequently asked questions
Where does a GitHub pull request template go?
Save pull_request_template.md in the repository root, docs/, or .github/ and merge it into the default branch. For multiple templates, use a PULL_REQUEST_TEMPLATE/ subdirectory in a supported location and select the file with GitHub's template query parameter.
Does this generator run my verification commands?
No. Commands remain text under a not-executed heading. Acceptance evidence is reported, not verified, and every generated review checkbox starts unchecked. Run checks yourself and record actual results and remaining gaps.
What if I only know the change area?
Change area is the only required field. Missing purpose, linked work, commands, risks or evidence become placeholders. The utility does not invent facts or interpret blank risk notes as an absence of risk.
How is this different from a handoff brief?
A handoff brief helps the next coding session resume work. This template helps a reviewer assess a proposed change through its purpose, linked work, verification, acceptance evidence and risks. It does not assign or approve the next coding task.
Is my input uploaded or shared automatically?
Generation runs in the browser without uploading input. Copy, Markdown export and Copy share link happen only on request. A share link contains your inputs in its URL fragment, readable by anyone with the link. Use non-secret drafting context; other website features have their own privacy behavior.
Related guides and tools
Record executed API contract evidence in a review
Draft acceptance criteria before reviewing evidence
Prepare a coding-session handoff instead
Review API contracts for AI development