Best PromptsCode Review
Review a diff like a senior engineer: verified, severity-ranked findings with concrete failure scenarios, no style nitpicks.
Review the code changes below as a senior engineer who will be paged if this breaks in production. For each finding, report: - **Severity**: blocker / major / minor - **Claim**: one sentence stating the defect - **Failure scenario**: the concrete input or state that triggers it and what goes wrong - **Fix**: the smallest change that resolves it Rules: - Only report findings you can defend with a failure scenario. "This could be cleaner" is not a finding. - Check specifically for: unhandled error paths, race conditions, off-by-one and boundary conditions, broken invariants across the codebase (callers of changed functions), security issues (injection, authz gaps, secrets), and silent data loss. - Skip formatting, naming preferences, and anything a linter catches. - If the diff looks correct, say so explicitly and state what you verified: an empty review with reasons beats invented nitpicks. Order findings most-severe first. Changes to review: """ [PASTE DIFF OR CODE] """
More coding prompts
Write the commit message for this change. Diff: """ [PASTE THE STAGED DIFF] """ Why I made this change: [THE REASON, THE TICKET, THE BUG REPORT, or "you infer it"] Convention: [Conventional Commits / this repo's existing style, pasted below / plain] Recent commits from this repo, to match style: """ [PASTE 5-10 RECENT COMMIT SUBJECT LIN
Commit Message
Write a commit message that explains why the change was made, in Conventional Commits format, split into separate commits when needed.
Codingbeginner
Help me recover from a git mistake without making it worse. What I was trying to do: [THE GOAL] What I ran: [THE EXACT COMMANDS, IN ORDER] What happened instead: [THE OUTPUT OR THE STATE NOW] Has this been pushed or shared: [YES/NO, and to which branch and whether anyone else has pulled] Uncommitted work I cannot lose: [WHAT AND WHERE, o
Undo a Git Mistake
Recover from a bad commit, force push, wrong branch, or lost work with a reversible plan and the exact commands, explained before you run them.
Codingintermediate
Handler code, routes, and models: """ [PASTE THE ROUTE DEFINITIONS, HANDLERS, REQUEST AND RESPONSE TYPES, VALIDATION SCHEMAS, AND MIDDLEWARE] """ Generate an OpenAPI 3.1 specification from the code above. API name, version, and base URL: [DETAILS] Auth scheme: [BEARER JWT / API KEY / OAUTH / SESSION COOKIE, and where it is enforced] Con
OpenAPI Spec From Code
Generate an accurate OpenAPI 3.1 spec from handler code, including error responses and auth, with gaps flagged instead of invented.
Codingintermediate