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

이 스킬 정보

적합한 상황: Perfect for Development Agents needing automated testing workflows with TDD and regression testing capabilities. 현지화된 요약: Boundary: CORE/testing-guide.md = philosophy (always loaded). This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

기능

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

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 8/11

This page remains useful for teams, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution
Review Score
8/11
Quality Score
36
Canonical Locale
en
Detected Body Locale
en

적합한 상황: Perfect for Development Agents needing automated testing workflows with TDD and regression testing capabilities. 현지화된 요약: Boundary: CORE/testing-guide.md = philosophy (always loaded). This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

이 스킬을 사용하는 이유

추천 설명: 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.

최적의 용도

적합한 상황: Perfect for Development Agents needing automated testing workflows with TDD and regression testing capabilities.

↓ 실행 가능한 사용 사례 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

! 보안 및 제한 사항

  • 제한 사항: 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

Why this page is reference-only

  • - Current locale does not satisfy the locale-governance contract.
  • - The underlying skill quality score is below the review floor.

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

Install Path

Start With Installation And Validation

If this skill is worth continuing with, the next step is to confirm the install command, CLI write path, and environment validation.
Trusted Recheck

Cross-Check Against Trusted Picks

If you are still comparing multiple skills or vendors, go back to the trusted collection before amplifying repository noise.
Workflow

Move To Workflow Collections For Team Rollout

When the goal shifts from a single skill to team workflows, approvals, and repeatable execution, move into workflow collections.
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. 현지화된 요약: Boundary: CORE/testing-guide.md = philosophy (always loaded). This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

How do I install tdd-qa?

Run the command: npx killer-skills add multicam/qara/tdd-qa. 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/tdd-qa. 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.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

tdd-qa

현지화된 요약: Boundary: CORE/testing-guide.md = philosophy (always loaded). This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

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.

관련 스킬

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

모두 보기

openclaw-release-maintainer

Logo of openclaw
openclaw

현지화된 요약: 🦞 # OpenClaw Release Maintainer Use this skill for release and publish-time workflow. It covers ai, assistant, crustacean workflows. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

★ 333.8k
⑂ 0
인공지능

widget-generator

Logo of f
f

현지화된 요약: Generate customizable widget plugins for the prompts.chat feed system # Widget Generator Skill This skill guides creation of widget plugins for prompts.chat . It covers ai, artificial-intelligence, awesome-list workflows. This AI agent skill supports Claude Code, Cursor, and Windsurf

★ 149.6k
⑂ 0
인공지능

flags

Logo of vercel
vercel

현지화된 요약: The React Framework # Feature Flags Use this skill when adding or changing framework feature flags in Next.js internals. It covers blog, browser, compiler workflows. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

★ 138.4k
⑂ 0
브라우저

pr-review

Logo of pytorch
pytorch

현지화된 요약: Usage Modes No Argument If the user invokes /pr-review with no arguments, do not perform a review . It covers autograd, deep-learning, gpu workflows. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

★ 98.6k
⑂ 0
개발자