tdd-enforcement
The tdd-enforcement skill mandates a strict Red-Green-Refactor test-driven development cycle with failing tests required before implementation, minimal code changes to pass tests, quality refactoring, and enforced 80% code coverage. Use this skill for all code implementation tasks, feature development, and bug fixes where test-first methodology ensures code quality and comprehensive test coverage.
git clone --depth 1 https://github.com/a5c-ai/babysitter /tmp/tdd-enforcement && cp -r /tmp/tdd-enforcement/library/methodologies/everything-claude-code/skills/tdd-enforcement ~/.claude/skills/tdd-enforcementSKILL.md
- Write tests that define expected behavior - Tests MUST fail (exit code 1) - Use CI=true or --run flag, never watch mode - Apply timeout guards (60s) to prevent hanging - Record exit code as evidence ### 2. GREEN Phase - Minimal Implementation - Write the minimal code to make tests pass - Do NOT add features not covered by tests - Do NOT optimize prematurely - Tests MUST pass (exit code 0) - Record exit code as evidence ### 3. REFACTOR Phase - Quality Improvement - Apply SOLID principles and clean code patterns - Improve naming, reduce coupling - Remove duplication - Run tests after EACH refactoring step - Tests MUST remain passing (exit code 0) ### 4. Coverage Gate - Measure coverage: statements, branches, functions, lines - Minimum 80% overall coverage required - Iterate: write additional tests for gaps until threshold met - Maximum 3 convergence iterations ## Rules - Never skip the RED phase - Never accept GREEN without exit code 0 - Never use watch mode in CI - Always record evidence (exit codes, coverage numbers) - Enforce 80% coverage threshold ## When to Use - All code implementation tasks - Feature development - Bug fixes (write regression test first) ## Agents Used - `tdd-guide` (primary consumer) - `code-reviewer` (validates test quality)
Coordinate Crew (persistent) and Polecat (transient) agents using Gas Town's hook-based work distribution and GUPP principle.
System and API design guidance covering component boundaries, data flow, integration patterns, and scalability considerations.
This skill should be used when the user asks to "find skills in the wild", "assimilate popular workflows", "discover SKILL.md files in repos", "research external skills", "find workflow patterns", "survey the skill landscape", "what skills exist out there", or wants to investigate public repositories for extractable processes, babysitter plugins, and reusable procedural insights. Searches GitHub for SKILL.md files, classifies repos by archetype, and maintains structured research under docs/reference-repos/.
>-
This skill should be used when the user asks to "babysit issues", "work on assigned issues", "check a5c-agent issues", "process babysitter issues", or wants to find and work on open GitHub issues assigned to a5c-agent in the babysitter repo.