tdd-workflow
SkillDev toolsTest-driven development discipline: RED (failing test) → GREEN (minimal code) → REFACTOR, delete-and-restart if production code was written first, and the test-type taxonomy (integration for API surfaces, unit for business logic, property for edge-case-heavy code). Load before starting a feature or bug fix, when reproducing a reported bug, or when deciding which kind of test a change needs.
Then ask your AI: use the tdd-workflow skill
Details
Instructions available. Your AI can read the instructions. Execution depends on the setup they require.
Account requirements not reviewed. Check the skill instructions before use; Ahel provides instructions and does not run this skill.
No other account needed.
Add it as a step in a pipeline you build on Ahel, or connect Ahel to Claude, ChatGPT, Cursor, Claude Code or Codex and ask your AI to use it.
What this skill tells your AI
The instructions your AI receives, as published by goldziher/ai-rulez in internal/builtins/universal/testing/skills/tdd-workflow/SKILL.md and read by Ahel’s review.
- Write the test before the code. Update the test when changing behaviour.
- Fixing a bug: write the failing test first, then fix. RED → GREEN → REFACTOR.
- Wrote production code before the test? Delete it and start over — no exceptions, don't keep it as reference.
- Integration tests for API surfaces, unit tests for business logic, property tests for edge-case-heavy code.
- Run the full test suite before committing — never push untested code.
Signals
- GitHub stars
- 159
- Forks
- 16
- Last commit
- Oct 2026
Advanced
- Item type
- skill
- Key
tdd-workflow-goldziher- Source
- github.com/goldziher/ai-rulez