AgentStack
SKILL verified MIT Self-run

Test Failure Triage

skill-jakesterns-agent-skills-test-failure-triage · by jakesterns

Diagnoses failing tests, separates product regressions from flaky or stale tests, and proposes minimal fixes with verification steps.

No reviews yet
0 installs
17 views
0.0% view→install

Install

$ agentstack add skill-jakesterns-agent-skills-test-failure-triage

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Test Failure Triage? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

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.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.