qa-investigation-harness
CLAUDE.md4 starsChanged 3 months agoMITView on GitHub
This repo has a risk-driven QA investigation harness. Full rules live in qa-harness/RULES.md — read it before running any stage below, and follow it exactly. Never write Playwright test code yourself. Test generation belongs to this project's test-generation agent (see qa-harness/RULES.md for how to get one if it doesn't exist yet) — this harness only investigates, produces a human-reviewed test plan, and audits the result. Invoke these as skills, in order: Stage 4 — actually generating tests — is not…
In this repository6 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .github/copilot-instructions.mdCopilot instructions
- qa-challengeSkill
- qa-exploreSkill
- qa-modelSkill
- qa-validateSkill
The file
We split this CLAUDE.md into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 7
Never write Playwright test code yourself.
≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.md 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 Investigation Harness
This repo has a risk-driven QA investigation harness. Full rules live in qa-harness/RULES.md — read it before running any stage below, and follow it exactly.
Never write Playwright test code yourself. Test generation belongs to this project's test-generation agent (see qa-harness/RULES.md for how to get one if it doesn't exist yet) — this harness only investigates, produces a human-reviewed test plan, and audits the result.
Stages
Invoke these as skills, in order:
/qa-explore— walk a flow, record observations (Stage 1)/qa-model— build a state/transition model (Stage 2)/qa-challenge— risk table, then (after human approval) a test plan (Stage 3)/qa-validate— audit generated tests against approved risks (Stage 5)
Stage 4 — actually generating tests — is not a skill here. Point your
project's test-generation agent at the specs/<ticket>.plan.md file Stage 3
produces, the same way you'd hand it any other plan.
See qa-harness/README.md for the full walkthrough.
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.