Appearance
qa-everything
qa-everything
qareadhands-off
Use this when: you want every QA pass run over a change at once
Problem it solves — Quality has several axes and you can't eyeball them all at once. This runs the QA passes together over a change, so tests, code conformance, and reasoning are all covered before a PR.
QA everything (quality sub-sweep)
The qa- family answers one question from four angles — does this meet our bar? This runs them together when you want a quality gate but not the whole check-everything machine.
What it runs (fixed order, applicable-only)
qa-tests— coverage holes (ZOMBIES / CORRECT, mutation) on the changed code.qa-code— conformance to rules + architecture, with the security/frontend lenses and severity tags, on the now-tested diff.qa-ui— only if the change touchedresources/js/**or a UI route — UI quality + assertable coverage (the page-surface manifest, the contract checklist) on the settled diff.qa-prompts— only if the change touchedresources/views/prompts/— correctness/safety of the prompt bodies.qa-philosophy— did the change make a foundational doc drift?qa-skills— only if the change touched.claude/skills/— is the set still coherent?
Order matters: tests before conformance (so qa-code judges the settled, tested diff); docs/skills after the code is right.
How it runs
Run each in turn, pausing after every one: a read-only finding asks "carry on, or dig in?"; an acting fix is proposed → you pick → it applies before the next runs. Skip any that doesn't apply and say so. The orchestrator writes nothing itself — every change stays behind its sub-skill's own confirm.
Orchestration (opt-in)
For a large, disjoint audit/fix set — many independent files or units — the sweep may fan out across cheap-model workers per the orchestration contract (docs/agents/orchestration.md), then synthesise in-thread. But a sweep over one shared diff (overlapping files) fails that doc's independence gate → stay in-thread. Default is in-thread; opt in only when it pays.
Where it sits
- A subset of
check-everything— the quality slice only. Reach forcheck-everythingwhen you also want reasoning, optimisation and housekeeping; reach here for a fast pre-PR quality pass. - Not a replacement for invoking a single
qa-skill when you know exactly which angle you need.