Best PromptsSystematic Debugging
Debug any failure methodically: reproduce, form ranked hypotheses, and identify the single cheapest test that discriminates between them.
Help me debug this issue. Work as a diagnostician, not a guesser. **Symptom**: [WHAT HAPPENS, INCLUDING EXACT ERROR TEXT] **Expected**: [WHAT SHOULD HAPPEN] **Started when**: [RECENT CHANGES, OR "unknown"] **Environment**: [RUNTIME, VERSIONS, OS] **What I've tried**: [ATTEMPTS SO FAR] Relevant code/logs: """ [PASTE] """ Do this: 1. Restate the symptom in your own words and list what the symptom RULES OUT: half of debugging is elimination. 2. Give your top 3 hypotheses, ranked by likelihood, each with the mechanism: "X causes Y because Z". 3. For the top hypothesis, give me the single cheapest experiment that would confirm or kill it (a log line, a one-line test, a command). Not a fix: a test. 4. Say what result to expect if the hypothesis is right, and what result means we move to hypothesis 2. Do not propose fixes until a hypothesis is confirmed. If you need information you don't have, ask for the specific command output instead of assuming.
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