analyzing-test-failures

Type: Pure reasoning — no system calls, no code authoring.

What it does: Parses a test failure or Code Analyzer violation payload and produces a plain-language explanation, then follows up with concrete, prioritized improvement suggestions per failed test — including whether each fix belongs in the test or in production code. Never exposes raw JSON, stack traces, or API error bodies to the user.

Prerequisites

If you need to fetch the failure payload yourself rather than receiving it, load checking-devops-prerequisites first, then use polling-test-results to obtain the execution result. If the payload is already in context, no prerequisites are needed — this is pure reasoning.

Inputs