For red builds where the stack trace does not obviously map to your change.
Here's a failing CI log: [paste]. Identify whether this is a flaky test, an environment/config issue, or a real code regression, and point to the exact evidence in the log.
Anything in square brackets is meant to be replaced. The builder turns those into fields you can type into.
Tired of re-pasting the same context into every new chat? That is what the Unimatrix MCP server is for.