tdd-qa — for Claude Code tdd-qa, community, for Claude Code, ide skills, mocking-guidelines.md, interface-design.md, write-scenarios, tdd-cycle, backtest, mutation-check

v1.0.0
GitHub

About this Skill

Perfect for Development Agents needing automated testing workflows with TDD and regression testing capabilities. File system based context manager

Features

Workflow Routing (SYSTEM PROMPT)
Set up testing: "set up testing", "init testing", "bootstrap test infra"
- READ: ${PAI DIR}/skills/tdd-qa/workflows/init-project.md
- EXECUTE: Copy templates, create specs/ dir, configure bunfig.toml
Define test scenarios: "write scenarios for X", "define test cases", "spec out the feature"

# Core Topics

for Claude Code mocking-guidelines.md interface-design.md write-scenarios tdd-cycle backtest
multicam multicam
[2]
[0]
Updated: 3/28/2026

Skill Overview

Start with fit, limitations, and setup before diving into the repository.

Perfect for Development Agents needing automated testing workflows with TDD and regression testing capabilities. File system based context manager

Core Value

Empowers agents to automate testing workflows using file system-based context management, supporting RED→GREEN→REFACTOR cycles, and regression testing with JUnit XML baselines, enforcing quality gates and providing mutation score analysis with StrykerJS.

Ideal Agent Persona

Perfect for Development Agents needing automated testing workflows with TDD and regression testing capabilities.

↓ Capabilities Granted for tdd-qa

Automating TDD cycles for new feature development
Running test pyramids for comprehensive test coverage
Debugging regressions with backtesting and quality gate enforcement
Verifying E2E browser functionality with devtools-mcp
Analyzing test effectiveness with mutation testing

! Prerequisites & Limits

  • Requires project initialization with 'init-project' workflow
  • Limited to supporting TDD and regression testing workflows
  • Dependent on specific file formats like JUnit XML for baselining

About The Source

The section below comes from the upstream repository. Use it as supporting material alongside the fit, use-case, and installation summary on this page.

Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is tdd-qa?

Perfect for Development Agents needing automated testing workflows with TDD and regression testing capabilities. File system based context manager

How do I install tdd-qa?

Run the command: npx killer-skills add multicam/qara. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for tdd-qa?

Key use cases include: Automating TDD cycles for new feature development, Running test pyramids for comprehensive test coverage, Debugging regressions with backtesting and quality gate enforcement, Verifying E2E browser functionality with devtools-mcp, Analyzing test effectiveness with mutation testing.

Which IDEs are compatible with tdd-qa?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for tdd-qa?

Requires project initialization with 'init-project' workflow. Limited to supporting TDD and regression testing workflows. Dependent on specific file formats like JUnit XML for baselining.

↓ How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add multicam/qara. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use tdd-qa immediately in the current project.

! Source Notes

This page is still useful for installation and source reference. Before using it, compare the fit, limitations, and upstream repository notes above.

Upstream Repository Material

The section below comes from the upstream repository. Use it as supporting material alongside the fit, use-case, and installation summary on this page.

Upstream Source

tdd-qa

Install tdd-qa, an AI agent skill for AI agent workflows and automation. Explore features, use cases, limitations, and setup guidance.

SKILL.md
Readonly
Upstream Repository Material
The section below comes from the upstream repository. Use it as supporting material alongside the fit, use-case, and installation summary on this page.
Upstream Source

Workflow Routing (SYSTEM PROMPT)

Set up testing: "set up testing", "init testing", "bootstrap test infra" -> READ: ${PAI_DIR}/skills/tdd-qa/workflows/init-project.md -> EXECUTE: Copy templates, create specs/ dir, configure bunfig.toml

Define test scenarios: "write scenarios for X", "define test cases", "spec out the feature" -> READ: ${PAI_DIR}/skills/tdd-qa/workflows/write-scenarios.md -> EXECUTE: Create Given/When/Then specs from requirements

Run a TDD cycle: "run TDD on X", "red green refactor", "TDD this feature" -> READ: ${PAI_DIR}/skills/tdd-qa/workflows/tdd-cycle.md -> EXECUTE: RED→GREEN→VERIFY loop with 2-retry escalation

Run test pyramid: "run the pyramid", "run all test layers", "full test suite" -> READ: ${PAI_DIR}/skills/tdd-qa/workflows/run-pyramid.md -> EXECUTE: Static→Unit→Integration→E2E in sequence

Check for regressions: "backtest", "check regressions", "compare test results", "quality gate" -> READ: ${PAI_DIR}/skills/tdd-qa/workflows/backtest.md -> EXECUTE: Compare JUnit XML baselines, check coverage delta, enforce gates

E2E browser verification: "verify E2E", "browser test", "e2e scenarios", "smoke test the UI" -> READ: ${PAI_DIR}/skills/tdd-qa/workflows/e2e-verify.md -> EXECUTE: Run scenarios via devtools-mcp, auto-draft .spec.ts

Mutation testing: "run mutation tests", "check mutation score", "how good are my tests" -> READ: ${PAI_DIR}/skills/tdd-qa/workflows/mutation-check.md -> EXECUTE: Run StrykerJS, report mutation score (advisory)

Philosophy/patterns/mocking: Not in this skill — see CORE testing-guide.md, mocking-guidelines.md, interface-design.md.

Boundary: CORE/testing-guide.md = philosophy (always loaded). This skill = executable blueprints (on-demand fork context).

Usage Modes

ModeFlow
New featurewrite-scenarios -> tdd-cycle -> backtest
Bug fixtriage-issue -> fix -> backtest
Confidencebacktest or run-pyramid
New projectinit-project (once)

Workflow steps are typed deterministic or agentic (Stripe Minions pattern). See references/blueprint-pattern.md.

Bombadil (v0.3.2) is experimental — invoke explicitly, not routed by default. → READ: workflows/explore-bombadil.md when user asks for Bombadil exploration.

Lifecycle Completion

Minimum Complete Cycle

  1. write-scenarios — Given/When/Then specs (mandatory human review gate at step 4)
  2. tdd-cycle — RED→GREEN→REFACTOR for each scenario
  3. backtest — regression check, baseline update

Complete when backtest passes with zero regressions and baseline updated.

Optional Extensions

ExtensionWhen to suggestPrerequisite
mutation-checkAfter backtest passes, for critical code pathsStrykerJS installed
e2e-verifyWhen feature has a browser UIdevtools-mcp available
run-pyramidBefore merging a PR, as final confidence checkTests exist at multiple layers

System-Level "Done"

A feature is fully tested when:

  • All quality gates pass (zero regressions, coverage not decreased)
  • Baseline updated
  • JM has reviewed and approved scenarios

Do not proactively run optional extensions unless JM asks or the feature touches critical code paths.

Composing Workflows

Canonical Sequences

Request typeSequenceSkippable steps
New featurewrite-scenarios → tdd-cycle → backtestwrite-scenarios skippable if JM provides inline requirements
Bug fixtdd-cycle (RED: failing test for bug) → backtestwrite-scenarios usually skipped for single bugs
Confidence checkbacktest or run-pyramidBoth standalone
Refactoringbacktest (before) → refactor → backtest (after)No TDD cycle — existing tests are the safety net

Ambiguous Requests

If a request spans multiple workflows, ask which workflow to start with rather than guessing. Example: "add auth and make sure nothing breaks" could mean write-scenarios + tdd-cycle + backtest, or just a confidence backtest on existing code.

Related Skills

Looking for an alternative to tdd-qa or another community skill for your workflow? Explore these related open-source skills.

View All

openclaw-release-maintainer

Logo of openclaw
openclaw

openclaw-release-maintainer is an AI agent skill for openclaw release maintainer.

★ 333.8k
⑂ 0
AI

widget-generator

Logo of f
f

Generate customizable widget plugins for the prompts.chat feed system

★ 149.6k
⑂ 0
AI

flags

Logo of vercel
vercel

flags is an AI agent skill for use this skill when adding or changing framework feature flags in next.js internals.

★ 138.4k
⑂ 0
Browser

pr-review

Logo of pytorch
pytorch

pr-review is an AI agent skill for pytorch pr review skill.

★ 98.6k
⑂ 0
Developer