ccc-testing
Load ONE skill. Get the entire testing domain. Built from 11 proven skills + 4 new ones.
Absorbed Skills Manifest
| # |
Original Skill |
What It Does |
Status |
| 1 |
e2e-testing |
Playwright end-to-end testing — page objects, fixtures, assertions, CI setup |
Absorbed |
| 2 |
webapp-testing |
Playwright for local web apps — dev server integration, visual testing |
Absorbed |
| 3 |
tdd-workflow |
Test-driven development — red/green/refactor cycle, coverage tracking |
Absorbed |
| 4 |
verification-loop |
Comprehensive verification — multi-step validation before marking done |
Absorbed |
| 5 |
verification-before-completion |
Proof-of-work verification — evidence that changes work correctly |
Absorbed |
| 6 |
ai-regression-testing |
AI-assisted regression — detect regressions using AI analysis of test results |
Absorbed |
| 7 |
eval-harness |
Eval-driven development — build evals first, then implement to pass them |
Absorbed |
| 8 |
qa |
Full QA pass — find bugs, fix them, commit fixes |
Absorbed |
| 9 |
qa-only |
Report-only QA — find and report bugs without fixing them |
Absorbed |
| 10 |
plankton-code-quality |
Write-time quality — catch issues as code is written, not after |
Absorbed |
| 11 |
python-testing |
Python testing — pytest, fixtures, mocking, TDD for Python projects |
Absorbed |
| 12 |
testing-router |
Routes your testing task to the right specialist |
NEW |
| 13 |
test-strategy |
Generates a complete testing strategy for any project |
NEW |
| 14 |
visual-regression |
Visual regression testing — screenshot comparison, Percy, Chromatic |
NEW |
| 15 |
load-testing |
Load testing — k6/Artillery scripts, performance benchmarks, stress testing |
NEW |
Replaces loading: e2e-testing, webapp-testing, tdd-workflow, verification-loop, verification-before-completion, ai-regression-testing, eval-harness, qa, qa-only, plankton-code-quality, python-testing
Routing Matrix
| Your Intent |
Route To |
Don't Confuse With |
| "Write tests first" / "TDD" |
tdd-workflow |
qa (testing existing code) |
| "E2E tests" / "Playwright" |
e2e-testing + webapp-testing |
tdd-workflow (unit level) |
| "Verify my work" / "Is this done?" |
verification-loop |
qa (broader scope) |
| "QA this" / "Find bugs" |
qa (fix) or qa-only (report) |
verification-loop (did I do this right?) |
| "Test strategy" / "What should I test?" |
test-strategy |
tdd-workflow (how to test) |
| "Visual regression" / "Screenshot tests" |
visual-regression |
e2e-testing (functional) |
| "Load testing" / "Performance test" |
load-testing |
visual-regression (visual) |
| "Check for regressions" |
ai-regression-testing |
visual-regression (visual only) |
| "Build evals" / "Eval-driven" |
eval-harness |
tdd-workflow (code tests, not evals) |
| "Python tests" / "pytest" |
python-testing |
tdd-workflow (language-agnostic) |
| "Code quality while writing" |
plankton-code-quality |
qa (post-hoc) |
Campaign Templates
Full Testing Strategy
test-strategy → analyze project, recommend test types and coverage targetstdd-workflow → set up test framework, write first testse2e-testing → critical user flow testsvisual-regression → screenshot baselinesload-testing → performance benchmarksverification-loop → verify everything passes
Bug Fix with Tests
qa or qa-only → identify the bugtdd-workflow → write failing test reproducing the bug- Fix the bug → test goes green
ai-regression-testing → check for related regressionsverification-before-completion → prove the fix works
Pre-Release QA
qa → full QA passe2e-testing → run full E2E suitevisual-regression → compare against baselinesload-testing → stress test under loadverification-loop → final sign-off
Scope note
This is the CLI catalog entry for the CCC testing domain. For the Desktop plugin entry, see commander/cowork-plugin/skills/ccc-testing/. Both dispatch to the same sub-skills.
TDD Feature Build
test-strategy → what to test for this featuretdd-workflow → red/green/refactor loope2e-testing → user flow testverification-before-completion → prove it works
1---2name: ccc-testing3description: CCC domain — complete testing ecosystem — 15 skills in one. TDD, E2E, verification, QA, regression, visual testing, and load testing.4---56# ccc-testing78> Load ONE skill. Get the entire testing domain. Built from 11 proven skills + 4 new ones.910## Absorbed Skills Manifest1112| # | Original Skill | What It Does | Status |13|---|----------------|--------------|--------|14| 1 | `e2e-testing` | Playwright end-to-end testing — page objects, fixtures, assertions, CI setup | Absorbed |15| 2 | `webapp-testing` | Playwright for local web apps — dev server integration, visual testing | Absorbed |16| 3 | `tdd-workflow` | Test-driven development — red/green/refactor cycle, coverage tracking | Absorbed |17| 4 | `verification-loop` | Comprehensive verification — multi-step validation before marking done | Absorbed |18| 5 | `verification-before-completion` | Proof-of-work verification — evidence that changes work correctly | Absorbed |19| 6 | `ai-regression-testing` | AI-assisted regression — detect regressions using AI analysis of test results | Absorbed |20| 7 | `eval-harness` | Eval-driven development — build evals first, then implement to pass them | Absorbed |21| 8 | `qa` | Full QA pass — find bugs, fix them, commit fixes | Absorbed |22| 9 | `qa-only` | Report-only QA — find and report bugs without fixing them | Absorbed |23| 10 | `plankton-code-quality` | Write-time quality — catch issues as code is written, not after | Absorbed |24| 11 | `python-testing` | Python testing — pytest, fixtures, mocking, TDD for Python projects | Absorbed |25| 12 | `testing-router` | Routes your testing task to the right specialist | **NEW** |26| 13 | `test-strategy` | Generates a complete testing strategy for any project | **NEW** |27| 14 | `visual-regression` | Visual regression testing — screenshot comparison, Percy, Chromatic | **NEW** |28| 15 | `load-testing` | Load testing — k6/Artillery scripts, performance benchmarks, stress testing | **NEW** |2930**Replaces loading:** e2e-testing, webapp-testing, tdd-workflow, verification-loop, verification-before-completion, ai-regression-testing, eval-harness, qa, qa-only, plankton-code-quality, python-testing3132---3334## Routing Matrix3536| Your Intent | Route To | Don't Confuse With |37|-------------|----------|--------------------|38| "Write tests first" / "TDD" | `tdd-workflow` | `qa` (testing existing code) |39| "E2E tests" / "Playwright" | `e2e-testing` + `webapp-testing` | `tdd-workflow` (unit level) |40| "Verify my work" / "Is this done?" | `verification-loop` | `qa` (broader scope) |41| "QA this" / "Find bugs" | `qa` (fix) or `qa-only` (report) | `verification-loop` (did I do this right?) |42| "Test strategy" / "What should I test?" | `test-strategy` | `tdd-workflow` (how to test) |43| "Visual regression" / "Screenshot tests" | `visual-regression` | `e2e-testing` (functional) |44| "Load testing" / "Performance test" | `load-testing` | `visual-regression` (visual) |45| "Check for regressions" | `ai-regression-testing` | `visual-regression` (visual only) |46| "Build evals" / "Eval-driven" | `eval-harness` | `tdd-workflow` (code tests, not evals) |47| "Python tests" / "pytest" | `python-testing` | `tdd-workflow` (language-agnostic) |48| "Code quality while writing" | `plankton-code-quality` | `qa` (post-hoc) |4950---5152## Campaign Templates5354### Full Testing Strategy551. `test-strategy` → analyze project, recommend test types and coverage targets562. `tdd-workflow` → set up test framework, write first tests573. `e2e-testing` → critical user flow tests584. `visual-regression` → screenshot baselines595. `load-testing` → performance benchmarks606. `verification-loop` → verify everything passes6162### Bug Fix with Tests631. `qa` or `qa-only` → identify the bug642. `tdd-workflow` → write failing test reproducing the bug653. Fix the bug → test goes green664. `ai-regression-testing` → check for related regressions675. `verification-before-completion` → prove the fix works6869### Pre-Release QA701. `qa` → full QA pass712. `e2e-testing` → run full E2E suite723. `visual-regression` → compare against baselines734. `load-testing` → stress test under load745. `verification-loop` → final sign-off7576## Scope note7778This is the **CLI catalog entry** for the CCC testing domain. For the Desktop plugin entry, see `commander/cowork-plugin/skills/ccc-testing/`. Both dispatch to the same sub-skills.7980### TDD Feature Build811. `test-strategy` → what to test for this feature822. `tdd-workflow` → red/green/refactor loop833. `e2e-testing` → user flow test844. `verification-before-completion` → prove it works
KevinZai