tdd

Enforce test-first implementation gates with red-green tests, coverage, and lint checks.

139|7|Updated May 8, 2026
One-click install
npx skills add https://github.com/arbiterForge/codeArbiter --skill tdd-arbiterforge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd
Source: https://github.com/arbiterForge/codeArbiter/tree/main/plugins/ca/skills/tdd
Command: npx skills add https://github.com/arbiterForge/codeArbiter --skill tdd-arbiterforge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents premature implementation by forcing code changes through a strict test-first workflow, so feature work, fixes, and refactors cannot slip past validation.

Core Features & Use Cases

  • Obligation Scanning: Derives the claims a change must satisfy before any implementation begins.
  • Red-Green Workflow: Requires failing tests first, then the smallest possible code change to make them pass.
  • Coverage and Lint Gates: Verifies that the finished work is exercised by tests, meets coverage expectations, and passes linting and type checks.
  • Use Case: When a developer needs to add a feature without breaking existing behavior, this Skill keeps the work disciplined, auditable, and ready for commit only after every gate is green.

Quick Start

Use the tdd skill to turn an approved change into failing tests first, then implement the smallest fix that makes every gate pass.

Frequently Asked Questions about tdd

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce test-first implementation gates for code changes?

Test-first implementation gates block code changes by requiring failing tests before any implementation begins. This ensures feature work, fixes, and refactors cannot slip past validation obligations.

What's the best way to maintain red-green test discipline during refactoring?

Red-green test discipline is maintained by requiring failing tests first, then implementing the smallest possible code change to make them pass, ensuring regression-safe implementation during refactoring workflows.

How does coverage auditing and lint gating work before committing code?

Coverage auditing and lint gating verify finished work by checking that tests exercise the code, meet coverage expectations, and pass linting and type checks before implementation is committed.

Can I use phase-ordered test mapping for feature development workflows?

Phase-ordered test mapping applies to feature development workflows by structuring obligations, red-green tests, coverage, and lint checks into strict validation phases before allowing implementation to proceed.

Why does append-only gate enforcement matter for test-driven development?

Append-only gate enforcement matters for test-driven development because it prevents bypassing validation gates, ensuring every phase-ordered test, coverage audit, and lint check passes before code is committed.

Does obligation scanning work for both fixes and new feature work?

Obligation scanning works for fixes and new feature work by deriving the specific claims a change must satisfy before any implementation begins, ensuring all code changes follow strict test-first validation.