Open Prompts
Submit a prompt
Coding

Debug a stack trace or error message

Paste the full error message and stack trace, the code where it originates, and what you were trying to do, and get back a plain-language explanation of what the error actually means. Returns likely causes ranked from most to least probable, points to the exact lines responsible, and suggests a minimal fix or next debugging step for each — including how you might be misusing a library if the trace points there.

Prompt
I'm getting the following error and don't understand what's causing it.

Error message and stack trace:
{{error_message}}

Relevant code:
{{code}}

What I was trying to do:
{{action}}

Explain, in plain language:
1. What this error actually means.
2. The most likely cause, ranked from most to least probable.
3. The exact line or lines most likely responsible.
4. A minimal fix or a next debugging step for each likely cause.

If the stack trace points to library or framework code, explain how my code is misusing it.
Download .md

Variables

Related prompts

Coding

Concurrency and race condition review

Paste code along with its concurrency model and the shared state involved for a review that skips general code-review concerns entirely and focuses only on concurrency. - Race conditions from unsynchronized read-modify-write or check-then-act patterns - Deadlock or livelock risk from lock ordering across threads or async tasks - Cleanup gaps under concurrent cancellation or failure - Each issue ships with the exact interleaving that triggers it, not a generic warning

Coding

Git commit message writer

Takes a pasted diff plus a short note on why the change was made, and returns a commit message ready to paste into git: an imperative summary line under 72 characters, followed by an optional body covering rationale and tradeoffs. It skips line-by-line narration in favor of describing intent and impact, and flags diffs that look like they're bundling unrelated changes that should be split into separate commits.

Coding

Regex generator and explainer

Describe a matching pattern in plain language, list a few strings it must reject, and name the language or regex engine, and get back a working regular expression. It comes with a token-by-token breakdown of what each part does, a callout of edge cases it might mishandle like unicode, empty strings, or catastrophic backtracking, and three example strings that should match plus three that shouldn't.