amia-tdd-enforcement

You can enforce TDD discipline in code reviews by validating test-first commits and tracking RED-GREEN-REFACTOR cycle transitions across PR workflows. This Skill audits commit history to detect violations and provides references for remediation when production code precedes test code.

A test-first commit verification workflow ensures tests are written before production code by auditing git commit history. It validates proper RED-GREEN-REFACTOR cycles, tracks transitions between phases, and governs PR merges to maintain strict TDD compliance across developer workflows.

Validating RED-GREEN-REFACTOR cycles across pull requests involves auditing commit history to ensure tests appear before implementation code. This Skill tracks cycle phase transitions, enforces test-first ordering at code review gates, and flags violations for remediation.

Yes, TDD enforcement applies to remote developer coordination by governing test-first commits across distributed PR workflows. It validates RED-GREEN-REFACTOR cycles regardless of developer location and provides remediation references when violations are detected during code review.

When TDD violations are detected in a PR, the Skill provides references and guidance for remediation. It identifies where production code preceded test code, flags the broken RED-GREEN-REFACTOR cycle sequence, and blocks progression until test-first discipline is restored.