Reading and Explaining a Stack Trace Workflow Prompt

Overview: Workflow prompt for Reading and Explaining a Stack Trace.

SOP Instructions

37 - READING AND EXPLAINING A STACK TRACE

Here is a stack trace or error output from this codebase. Explain it in plain language before proposing any fix.

For each meaningful frame, provide:

1) what that frame is responsible for,
2) how it relates to the frame above and below,
3) whether it is application code, framework code, or library code,
4) whether it is likely the cause or a symptom.

Then identify:

- the exact origin of the error,
- the user action or request that triggered it,
- the first place where something went wrong,
- any missing context that would help understand it.

End with:

- your top hypothesis,
- your confidence level,
- a specific log or debug statement that would confirm the hypothesis.