qa-triage
Skill1 starsChanged 2 months agoMITView on GitHub
Entry point for any ambiguous quality request. Classifies the ask into one of six QA jobs, scopes it to the real risk surface, and routes to the right skill. Use when the request is vague ("improve our testing", "make this reliable", "QA this") or when several QA jobs are tangled in one sentence.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- uppadhyayraj/dq-awesomeqatheir own version, first seen Oct 13, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- uppadhyayraj/dq-awesomeqa★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository34 other files it gives its agents.
- a11y-auditSkill
- api-contract-testingSkill
- autonomous-explorationSkill
- bug-reproSkill
- chaos-resilienceSkill
- ci-wiringSkill
- contract-testing-pactSkill
- coverage-ratchetSkill
- database-testingSkill
- e2e-authoringSkill
- environment-paritySkill
- exploratory-chartersSkill
- false-positive-hunterSkill
- flake-forensicsSkill
- i18n-l10n-testingSkill
- load-and-stressSkill
- mutation-proofSkill
- never-break-prodSkill
- payment-testingSkill
- perf-budgetSkill
- regression-curationSkill
- release-gateSkill
- responsive-mobile-testingSkill
- risk-mapSkill
- root-cause-protocolSkill
- security-regressionSkill
- smoke-and-sanitySkill
- state-machine-testingSkill
- test-data-managementSkill
- test-strategySkill
- tracking-testingSkill
- transactional-email-testingSkill
- unit-test-authoringSkill
- visual-regressionSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 28
Scope it: Ask exactly one question if — and only if — the answer changes the route:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
QA Triage
Most quality requests arrive tangled: "the checkout is flaky and we have no tests and I think there's a bug". Three jobs, three different skills, one wrong order away from waste.
The six jobs
| Job | Signal | Route |
| Decide what to test | no suite, or suite with no rationale | risk-map → test-strategy |
| Create tests | feature exists, coverage missing | unit-test-authoring / api-contract-testing / e2e-authoring |
| Judge existing tests | suite exists, trust is low | false-positive-hunter → mutation-proof |
| Stabilize | tests pass sometimes | flake-forensics |
| Diagnose | something is broken | root-cause-protocol → bug-repro |
| Gate | a release decision is pending | release-gate |
Procedure
- Split the ask. Rewrite the request as one line per job. Show the list.
- Order by dependency, not by mention. Diagnose before Create (a test written against broken behavior enshrines the bug). Judge before Create when a suite already exists (adding tests to a false-positive suite multiplies the lie). Gate last, always.
- Scope it. Ask exactly one question if — and only if — the answer changes the route:
- What is the blast radius: a diff, a feature, a service, the product?
- Is there a deadline that forces triage over completeness?
- State the plan in three lines max, then start job one. Do not narrate the rest.
Anti-patterns this skill exists to prevent
- Writing tests before reproducing a reported bug — you encode the defect as expected.
- Chasing coverage % when the suite has never caught a regression.
- Stabilizing a flaky test that asserts nothing (delete it instead — see
false-positive-hunter). - Running every QA skill "to be thorough". Thoroughness is depth on the right target.
Output
JOBS: <n>
1. <job> -> <skill> [scope: <files/feature>]
2. ...
STARTING: <job 1>. Reason: <one clause>.Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.