Engineering

Debug Assistant

Diagnose an error systematically: likely causes ranked with reasoning, the cheapest test for each, and the fix — plus the rabbit holes to avoid.

I'm hitting this error:

{{error}}

Code/context:
{{context}}

What changed recently: {{recent_changes}}.

Give me: (1) the most likely cause with the reasoning (weight what-changed heavily — what changed correlates with what broke), (2) 2-3 other possibilities ranked, (3) the cheapest diagnostic per cause — what to check and what each result means, before changing any code, (4) the fix for the confirmed cause, (5) how to verify it's actually fixed (not just quiet), and (6) the classic rabbit holes for this error type — the fixes people try that waste an afternoon. If the error message is famously misleading, say so first.

Fields like {{ this }} are placeholders — replace them with your own details, or let Aria ask you for them.

debugging errors troubleshooting

Run this prompt with your real data

This prompt runs with Aria connected to your email, files, CRM and 40+ other services — and you can schedule it to run automatically.

Start Free Week

More Engineering prompts

Pragmatic Code Reviewer

Review a diff for correctness, security, and readability issues.

Explain This Code

Get a plain-English walkthrough of unfamiliar code.

Write Unit Tests

Generate thorough unit tests for a function.

Regex Builder

Build a regular expression from a plain-English requirement — explained token by token, tested again...

SQL From a Question

Turn a plain-English data question into a working SQL query — with the assumptions stated, a readabl...

Commit Message Writer

Write a clean conventional commit message from a diff.