Loading page
About this tool
Generate a code review checklist tuned to your language, change type and risk level, ready to paste into a pull request.
This generator builds a code review checklist matched to your language, change type and risk level, output as Markdown task boxes ready for a pull request template. Its core sections — design, functionality, complexity, tests and documentation — follow Google's Code Review Developer Guide, and its security items follow the OWASP Code Review Guide. Reviewers and tech leads get a focused list instead of a generic wall of questions.
Open Code Review Checklist Generator on AltFTool — it loads instantly in your browser.
Paste your code or data sample into the workspace.
Pick the format, conversion, or analysis you need.
Copy the polished result straight back into your project.
Items change with the language, the change type (feature, bugfix, hotfix, dependency, config) and what the diff touches.
Sections mirror Google's Code Review Developer Guide; security items follow the OWASP Code Review Guide.
Output uses `- [ ]` task syntax that renders as tickable checkboxes on GitHub, GitLab and Bitbucket.
Design fit, correctness and edge cases, readability, test coverage and documentation — the categories in Google's Code Review Developer Guide — plus targeted items for whatever the change touches: security, database migrations, API contracts, UI accessibility, performance or concurrency. This generator assembles exactly those sections based on your selections.
Around 400 changed lines or fewer per session. The widely cited SmartBear study of 2,500 code reviews at Cisco found defect discovery drops sharply beyond 400 lines, and review effectiveness is best under 60–90 minutes at a time. The generated checklist includes this guidance in its header.
Security checks belong in any review where the change handles user input, authentication, authorization or secrets — the focus areas of the OWASP Code Review Guide. For diffs that touch none of those, a shorter checklist keeps reviews fast; this tool lets you toggle the security section per change.
Put the generated Markdown in a PULL_REQUEST_TEMPLATE.md file at the root, in .github/, or in docs/ of your repository — GitHub, GitLab and Bitbucket all pre-fill new pull requests from it. The `- [ ]` items render as interactive checkboxes that reviewers can tick off.