test-failure-triage

name	test-failure-triage
display_name	Test Failure Triage
description	Diagnoses failing tests, separates product regressions from flaky or stale tests, and proposes minimal fixes with verification steps.
category	testing
version	1.0.0
tags	["testing","debugging","flaky-tests","ci","regression"]
providers	["claude-code","codex","copilot","openclaw","hermes-agent"]
author	agent-skills contributors

Test Failure Triage

Use this skill when tests fail locally or in CI and the user needs root cause analysis, not just a quick patch.

Inputs

• Test output, stack traces, CI logs, failing test names, and recent changes
• Relevant source files and test files
• Test command and environment details when available

Steps

1. Identify the first meaningful failure, ignoring downstream failures caused by setup or earlier errors.
2. Classify the failure: product regression, test expectation drift, flaky timing, environment issue, fixture/data issue, dependency issue, or infrastructure failure.
3. Trace the failing assertion back to the behavior it protects.
4. Compare recent code changes against that behavior.
5. Recommend the smallest fix that preserves the intended behavior.
6. If the test is stale, explain why and update the expectation only when the new behavior is intentional.
7. Provide verification commands and any follow-up tests to prevent recurrence.

Output

Return:

• Root cause summary
• Failure classification
• Minimal fix plan
• Files likely needing changes
• Verification commands
• Flake or environment notes if relevant

Guidelines

• Do not delete or weaken tests just to make CI pass.
• Treat intermittent failures as real until evidence shows otherwise.
• Preserve the diagnostic value of the test suite.