Skip to content

/test-triage

Testing class

Writes test source into the repo and executes it — the only class that does both. Shared rules: CONVENTIONS-testing.md.

Use this skill when the user asks \"why did the tests fail\", \"is this a real bug or a flake\", \"triage the CI failures\", or wants a red build explained rather than re-run. Reads the run manifest from /e2e-run, the diff since last green, and the flake ledger, then classifies each failure as real defect, test bug, environment, flake, or data — each with a confidence and the evidence it cites. Correlates failures to suspect commits by blaming the changed lines. Advises only: it writes nothing, fixes nothing, and hands real defects to /pm-task.

At a glance

Run it /test-triage
Class testing
Version 0.1.0
Author navjyotnishant
Needs a run manifest from /e2e-run · git · the flake ledger (§T14) · gitleaks or trufflehog or detect-secrets
Source skills/test-triage/SKILL.md

What it needs, and what happens without it

Every tool is detected at runtime — none is installed for you.

Tool Without it
a run manifest from /e2e-run BLOCK — there is nothing to triage without it
git classify without commit correlation, and say so
the flake ledger (§T14) say the flake class is unavailable — never guess it from one run
gitleaks or trufflehog or detect-secrets BLOCK before publishing anything

Agents it spawns

This skill spawns no subagents — it runs inline.

The procedure

The executable steps live in the skill file itself and are deliberately not reproduced here: they are instructions to the model at runtime, not documentation.

Read test-triage/SKILL.md →