debugging
Finding the cause of a failure.
7 tagged items
- CheatsheetClaude
Claude Code commands worth knowing
The slash commands that save the most time, from your first CLAUDE.md to reviewing a diff before it ships.
Tested on Claude Sonnet · Sep 2026
- ErrorChatGPTGemini
This model's maximum context length is N tokens
The request is longer than the model can hold. Your prompt, the whole conversation history and the space reserved for the answer all count. The…
Tested on GPT-5 · May 2026
- PromptUniversal
Check a SQL query for what it actually does before running it
Explains a query in plain language and flags anything destructive or unbounded. Use it before you run something you did not write against a real…
- ErrorChatGPT
429 Too Many Requests / Rate limit reached
You crossed a request or token limit for your tier. Backoff with jitter and batching fix it. A shorter sleep does not, and the response header tells…
Tested on GPT-5 · May 2026
- PromptUniversal
Turn a vague bug report into concrete reproduction steps
Takes an unstructured user report and produces a numbered sequence an engineer can follow, with anything the report does not specify marked.
- PromptUniversal
Debug from a stack trace
Works from the trace and the relevant source to name the most likely cause, with the check that would confirm it.
- PromptUniversal
Strict code review of a diff
A review prompt that reports only what would break in production, gives the smallest fix for each finding, and is allowed to say the diff is fine.