ccc-qalisted

# /ccc-qa — Comprehensive QA Workflow Full QA pass before shipping. Detects test framework, runs all suites, reports coverage delta, flags edge cases and flaky tests. Delegates analysis to the `qa-engineer` subagent. Never marks QA passed with open 🔴 Critical findings. ## Triggers - `/ccc-qa` or `/qa` - "QA pass", "run all tests", "test coverage check" - "before shipping", "pre-release checks", "is this ready to ship" - "check test coverage", "find missing tests" - "flaky test", "test suite health" - Coming from `/ccc-review` or `/ccc-ship` ## When NOT to Use - Greenfield project with no tests yet — use `/ccc-testing` to scaffold the test suite first - Single-function bug fixes where a targeted unit test is the right move (write it directly) - Pure documentation or config-only changes with no testable behavior ## Process ### Step 1 — Detect test framework Run the following in parallel via `Bash`: ```bash # Detect JS/TS frameworks cat package.json 2>/dev/null | grep -E '"(vitest|jest|playwright|mocha|cypress|jasmine)"' | head -10 # Detect config files ls *.config.{ts,js,mjs} vitest.config.* jest.config.* playwright.config.* pytest.ini setup.cfg \ go.mod Cargo.toml pom.xml 2>/dev/null # Detect Python python3 -m pytest --collect-only -q 2>/dev/null | tail -5 # Detect Go go test ./... -list '.*' 2>/dev/null | head -10 # Detect Rust cargo test --no-run 2>/dev/null | tail -5 # Baseline coverage (if previously run) cat .ccc/coverage-history.json 2>/dev/null || cat