Prompt catalog
Browse reusable AI prompts by topic, then open any prompt to copy and adapt it for your workflow.
375 prompts · page 23 of 42
Describe the issue you've spotted in plain English along with the specific lines and fuller details, and get back a ready-to-paste GitHub review comment instead of staring at a blank comment box. The output is specific, explains why the issue matters, includes a concrete suggested fix, and skips filler openers like "Great work, but..." — also useful as a template for junior reviewers learning to write good comments.
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
Plans a framework, database, or API migration from your current setup to a target one, honoring the compatibility window, downtime limit, and behavior you say must be preserved. - Takes old/new stack, current and target setup, and hard constraints as input - Outputs an ordered migration checklist, tackling the riskiest changes first - Generates code transformations for common patterns and lists breaking changes - Includes a rollback plan and validation tests to confirm the migration worked
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