Loading page
About this tool
Generate a GitHub pull request template with summary, checklist, testing notes and screenshots sections, ready for .github/.
This tool generates a ready-to-commit GitHub pull request template — a Markdown file saved as .github/pull_request_template.md that pre-fills every new PR description with summary, linked-issue, testing, screenshot and checklist sections. It follows GitHub's documented template locations and closing-keyword syntax, so issues linked with "Closes #123" are closed automatically on merge. It is built for maintainers and team leads who want consistent, reviewable pull requests without writing the boilerplate by hand.
Open Pull Request Template Generator on AltFTool — it loads instantly in your browser.
Provide your input — an image, text, or data.
Let the tool analyze or generate the result.
Review, refine, and reuse the output wherever you need it.
Outputs the exact .github/pull_request_template.md path GitHub scans, or a named file under PULL_REQUEST_TEMPLATE/ for multi-template repos.
Frontend, backend, library and general presets plus your own custom items, all as tickable task-list checkboxes.
Includes the Closes # keyword pattern so merged PRs close their linked issues automatically.
Save it as pull_request_template.md in the repository root, the docs/ folder, or the .github/ folder of your default branch — .github/ is the common choice. The filename is case-insensitive, and the template must be merged into the default branch before GitHub starts using it.
Yes. Put each template as its own .md file inside a PULL_REQUEST_TEMPLATE/ subdirectory (for example .github/PULL_REQUEST_TEMPLATE/feature.md), then select one when opening a PR by adding ?template=feature.md to the compare URL. There is no automatic picker in the UI, so teams usually document the URLs in CONTRIBUTING.md.
Use a closing keyword followed by the issue number in the PR description — close, closes, closed, fix, fixes, fixed, resolve, resolves or resolved, as in "Closes #123". When the PR merges into the default branch, GitHub closes the referenced issue; the template generated here includes a Linked issues section with this pattern.
They render as interactive task lists: anyone with edit access can tick them after the PR is opened, and GitHub shows task completion progress in PR lists. They are not enforced by GitHub itself, but many teams pair them with CI bots or required reviews that check the boxes are complete before merge.