qa-report
Skill2 starsChanged 7 days agoApache-2.0View on GitHub
Aggregate the evidence directory into QA metrics — pass rate, P0/P1 trend, BLOCKED reasons, routing quality, learning throughput, per project and product. Use for "/qa-report", weekly/sprint summary, "QA-Bericht", "Testreport", "wie läuft's mit dem Testing". Not for a single ticket's verdict — /report-to-jira.
8 other projects use a version of this.
Adopted by
Most recently taken up by
- compozy/compozytheir own version, first seen Nov 13, 2026
- jianjian12138/test-skillstheir own version, first seen Oct 25, 2026
- uppadhyayraj/dq-awesomeqatheir own version, first seen Oct 13, 2026
- raoofaltaher/ultrapowerstheir own version, first seen Oct 11, 2026
- salesforce/cloudsplainingtheir own version, first seen Oct 8, 2026
- VodouAI/OStheir own version, first seen Jul 19, 2026
Other versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 8
- compozy/compozy★ 2.9ksame name
- salesforce/cloudsplaining★ 2.3ksame name
- pedronauck/skills★ 655same name
- raoofaltaher/ultrapowers★ 2same name
- uppadhyayraj/dq-awesomeqa★ 2same name
- napnap11/claude-skills★ 1same name
- VodouAI/OS★ 1same name
- jianjian12138/test-skills★ 0same 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.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- accessibility-testingSkill
- agentswitchSkill
- api-testingSkill
- bug-reportSkill
- bug-reproductionSkill
- demoSkill
- deploy-to-stageSkill
- exploratory-testingSkill
- failure-analysisSkill
- model-setupSkill
- onboard-productSkill
- onboard-projectSkill
- perf-analysisSkill
- qa-helpSkill
- qa-metricsSkill
- re-boardSkill
- reconSkill
- release-readinessSkill
- report-to-jiraSkill
- retest-bugSkill
- retro-learnSkill
- risk-based-testingSkill
- scaffold-suiteSkill
- security-testingSkill
- skill-reviewSkill
- test-automationSkill
- test-case-managementSkill
- test-reliabilitySkill
- test-ticketSkill
- visual-testingSkill
- webdriverio-testingSkill
- whats-newSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 0 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 9
Every run writes execution_summary.json.
- Very specific: line 16
Run the aggregator (it reads only evidence/, writes nothing):
- Very specific: line 24
Read the output and interpret it against the project's own gates — the defaults in .claude/rules/core/qa-principles.md are overridden per …
“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/qa-report — what the runs already know
Every run writes execution_summary.json; nothing ever read one back. This skill
turns that pile into the numbers a QA lead, a release manager or a retro actually
asks for. No new data source, no MCP server, no process change — just the evidence
that is already there.
Steps
Run the aggregator (it reads only
evidence/, writes nothing):python3 .claude/skills/qa-report/aggregate.py --since 30 # --project SHOP one project only # --json machine-readable, for a dashboard or a pipeline- Read the output and interpret it against the project's own gates — the
defaults in
.claude/rules/core/qa-principles.mdare overridden per project inPROJECT.md→ "Pipelines / quality gates", and a product may tighten them further. A pass rate of 88 % is a breach in a project that declared ≥ 90 % and fine in one that declared ≥ 80 %. Never report a number without the gate it is measured against. - Turn the two blueprint-specific columns into actions, because they are the ones
nobody else will read:
- Routing needed a human — every
user,defaultorsecondaryresolution is a missing component/label row in the project's registry. Propose the rows;retro-learnpromotes them (.claude/rules/core/product-layer.md). - Awaiting ruling — every
test-outdatedortest-brittlefailure still waiting on a human is a test the suite is currently lying about. One or two is normal traffic; a number that grows week over week means the suite is drifting away from the product, and the fix is a grooming session with the test owners, not a metric. Report the count and the age of the oldest, never a percentage. - Undeclared learnings — a run that produced evidence without declaring its
learningsmeans the evidence gate did not fire. That is an enforcement gap, not a reporting detail: check that the gate is wired in this repo before trusting any other number in the report.
- Routing needed a human — every
- Deliver it where the audience is. A QA lead does not read ticket comments:
- a published page for the team (offer it — the report is Markdown already),
- a Confluence page update if the project keeps one (per
PROJECT.md→ "Confluence"; note that editing Confluence is an explicit, separate request, not something this skill does on its own), - or a JIRA comment on the project's regression ticket, per
report-to-jira.
- Anything the report reveals about the blueprint itself (a metric that is always
empty, a scope that never appears) is a
retro-learncapture.
What this skill does not do
Invent metrics the schema cannot support. The aggregator prints an explicit "not
computable" section — defect escape rate and coverage are not derivable from
execution_summary.json, and the flake rate covers only runs that reported
test_cases[] (the CLI runner; never an exploratory session). Estimating the rest
anyway would produce exactly the kind of sourced-looking-but-wrong number this
blueprint keeps warning about. The flake rate is the worked example of the right
order: the schema grew attempts first, then the aggregator started counting.
It also does not judge people. The unit of every number here is a run, not a tester.
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.

