Tag
Before anything ships, it helps to have a second pair of eyes. These prompts turn ChatGPT or Claude into that reviewer, flagging issues and ranking them by how much they matter.
25 prompts · page 2 of 3
Paste code to get a complexity-reduction pass that swaps over-engineered solutions and hand-rolled reimplementations for built-in language or library features. The simplified version is shown side by side with the original, and only genuine simplifications are suggested — if a change would alter behavior in edge cases, or the code is already about as simple as it can get, it says so instead of forcing a rewrite.
Paste a diff to get a review that stays narrowly focused on logic errors, null dereferences, race conditions, and off-by-one bugs — the kind that actually reach production — while ignoring formatting and naming entirely. Each bug found comes with the exact line, why it's a bug, and a suggested fix, and it says so explicitly if nothing turns up rather than padding the review with style notes.
Paste a diff or function to get a systematic sweep of the edge cases it doesn't handle, before you sit down to write tests. - Covers empty inputs, nil/null values, boundary values (0, -1, MaxInt), concurrent access, timeouts, and malformed data - For each gap, shows what currently happens versus what should happen instead - Follow up with "write a test for the three most dangerous ones" to get code immediately
Paste a diff to catch the error-handling bugs that trigger 2am incidents — the ones that don't throw or log, just quietly corrupt state or return wrong data. It scans for swallowed exceptions, unchecked error returns, missing error paths, and logged-but-ignored failures, then rates overall error handling 1-10 with the reasoning behind the score so you know whether to approve or request changes.
Feed in a slow or clunky piece of code and get back concrete optimization options instead of a rewritten version to trust blindly. - The specific change and where it applies - The expected performance improvement - Any trade-offs it introduces, such as readability, memory, or complexity - Useful as a first pass before profiling, or as a sanity check on optimizations you're already considering
A broad first-pass review for a pasted code block that hasn't been looked at by anyone else yet, no special setup or context required beyond the code itself. It checks quality and best practices, likely bugs and edge cases, performance, readability, and security in one sweep, then explains the reasoning behind every suggestion so it teaches as much as it fixes.
Scores a pull request on long-term maintenance cost rather than just correctness, useful for code that works today but already smells expensive to keep. - Rates readability, complexity, dependency risk, and change isolation from 1-10 - Surfaces the top 3 maintainability concerns behind those scores - Suggests concrete ways to simplify each one before merge
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
A fixed, project-specific checklist for reviewing changes in a React/TypeScript plus FastAPI/Python codebase, not a generic "review this code" prompt. - Frontend: React Flow node patterns, Zustand store selectors, design tokens - Backend: Pydantic model layering, FastAPI auth dependencies, response models - Also covers security, performance, test coverage, docs, and commit hygiene - Reach for it before merging, to keep reviews consistent across the team