Open Prompts
Submit a prompt
Coding

Comprehensive Code Review Checklist

Paste code along with its purpose, stack, module, and constraints to get a full-spectrum review covering correctness, security, performance, maintainability, error handling, accessibility, and test coverage in one pass. Returns a severity-ranked issues table, the top 3 priorities, positive observations, and specific tests to add — built to run right before merging a PR or handing code to a peer reviewer.

Prompt
You are a senior software engineer.

Review this code.

Code:
{{code}}

Context:
- Purpose: {{purpose}}
- Stack: {{stack}}
- Feature or module: {{module}}
- Constraints: {{constraints}}

Review these categories:
1. Correctness.
2. Security.
3. Performance.
4. Maintainability.
5. Error handling.
6. Accessibility or UX if relevant.
7. Test coverage.

Output:
- Summary.
- Issues table with severity, location, issue, fix.
- Top 3 priorities.
- Positive observations.
- Tests to add.

Rules:
- Do not focus on formatting unless it affects readability.
- Be specific.
- If no issue exists in a category, say so.
Download .md

Variables

Related prompts

Coding

Balanced Senior Engineer PR Review

Give it the PR's stated goal and your repo's architecture and conventions to get a review that avoids both rubber-stamping and nitpicking. It checks correctness, readability, maintainability, test coverage, and backward compatibility in one pass, then sorts findings into Confirmed Issues, Possible Risks, and Nice-to-Haves, closing with three ready-to-paste GitHub review comments.

Coding

Missing Unit Test Generator

Reads a pasted diff and writes the unit tests it's missing, in your stated test framework, as runnable code rather than a bulleted test plan. - Covers the happy path, the top 3 edge cases, and at least one failure scenario - Uses realistic sample data instead of placeholder strings like "foo" - Tip: ask it to also write a test that would have caught the bug, if the diff is a fix

Coding

Test Coverage Gap Finder

Reviews a PR the way a strict test reviewer would when the code looks fine but the test coverage feels shaky. It calls out missing negative and boundary tests, gaps in integration coverage, flaky test risks, and spots where implementation changed but the matching tests didn't. Returns the critical missing tests first, then useful additional ones, described as sample test cases in plain English.