Diagnose a failing CI pipeline
Find why a build or pipeline fails in CI but not locally, and get the exact change to fix it.
Turn an error message and stack trace into ranked root-cause hypotheses, quick checks to confirm each, and a fix.
Help me find the root cause of an error in a {{language}} application.
Stack: {{stack}}
What I was doing when it happened: {{trigger}}
What I have already tried: {{tried}}
Error and stack trace:
{{trace}}
Relevant code (if any):
{{code}}
Work through it like this:
1. Read the trace from the bottom up and identify the first frame that is in my own code. Explain in plain words what that line was doing when it failed.
2. Give the 3 most likely root causes, ranked by probability. For each, give the evidence in the trace or code that supports it and one quick check (a log line, a debugger watch, a command) that would confirm or rule it out.
3. For the top candidate, show the fix as a minimal code change.
4. Say what additional information would change your ranking.
5. Suggest one guard, assertion or test so this class of bug is caught earlier next time.
Do not rewrite unrelated code. If the trace is truncated or the cause cannot be determined from what I gave you, say so and tell me exactly what to send next.Asking for ranked hypotheses with a cheap confirming check each stops the model from jumping to one confident guess. Including what you tried avoids repeated advice.
Licensed CC0 (public domain) Version 1 · history
Find why a build or pipeline fails in CI but not locally, and get the exact change to fix it.
Systematically narrow down why a test or bug only fails sometimes, with experiments to prove the cause.
Turn vague customer descriptions into a structured bug report with severity, reproduction steps, likely area and missing information.
Draft a clear, tight system prompt that tells an AI coding assistant how to work in your repository.
Get a prioritized code review that separates real defects from style nits, with a concrete fix for each issue.
Make tangled code easier to read and change without altering behavior, with every edit explained.
Comments (0)
Sign in to join the discussion.
No comments yet. Be the first to share how it worked.