KevinZai ccc-testing
Load ONE skill. Get the entire testing domain. 15 skills in one.
Default isolation: worktree — test dispatches run in an isolated worktree to avoid polluting the working tree.
What's Inside
| Category | Skills |
|---|---|
| Foundation | testing-router, test-strategy |
| Unit & TDD | tdd-workflow, plankton-code-quality, python-testing |
| Integration & E2E | e2e-testing, webapp-testing |
| Visual & Performance | visual-regression, load-testing |
| Quality Assurance | qa, qa-only, ai-regression-testing |
| Verification | verification-loop, verification-before-completion, eval-harness |
No expressed intent? Present the top 3 sub-skills + "More…" as an AskUserQuestion picker (≤4 options).
Routing Matrix
| Your Intent | Route To |
|---|---|
| "Write tests first" / "TDD" | tdd-workflow |
| "E2E tests" / "Playwright" | e2e-testing + webapp-testing |
| "Verify my work" / "Is this done?" | verification-loop |
| "QA this" / "Find bugs and fix" | qa |
| "Find bugs but don't fix" | qa-only |
| "Test strategy" / "What should I test?" | test-strategy |
| "Visual regression" / "Screenshot tests" | visual-regression |
| "Load testing" / "Performance test" | load-testing |
| "Check for regressions" | ai-regression-testing |
| "Build evals" / "Eval-driven" | eval-harness |
| "Python tests" / "pytest" | python-testing |
Campaign Templates
Full Testing Strategy (New Project)
test-strategy→ analyze project, recommend test types + coverage targetstdd-workflow→ set up framework, write first testse2e-testing→ critical user flow testsvisual-regression→ screenshot baselinesload-testing→ performance benchmarksverification-loop→ verify everything passes
Bug Fix with Tests (TDD Protocol)
qaorqa-only→ identify the bugtdd-workflow→ write failing test reproducing the bug- Fix → 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 Desktop plugin entry for the CCC testing domain. For the CLI/catalog entry, see skills/ccc-testing/. Content is kept in sync via the same router contract.
When to invoke this skill
Example 1
- user: write tests for this auth module using TDD
- assistant: Loads ccc-testing and routes to tdd-workflow — writes failing tests first, then implements to pass them.
Example 2
- user: run a full QA pass before the release
- assistant: Loads ccc-testing and runs pre-release pipeline: qa → e2e-testing → visual-regression → load-testing → verification-loop.
Example 3
- user: set up Playwright E2E tests for our checkout flow
- assistant: Loads ccc-testing and routes to e2e-testing + webapp-testing with page objects and CI integration.
⚙️ Fable contract: plan before build · verifier ≠ worker · prove before alarm · loops need gates · leave durable state —
rules/fable-method.md
(On Codex, present these options as a numbered list and ask the user to reply with a number — AskUserQuestion is Claude-only.)