Guide test-first implementation of TypeScript features and bug fixes.
npx skills add https://github.com/dmmulroy/skills --skill tdd-dmmulroy
Please help me install this Agent Skill. Skill: tdd Source: https://github.com/dmmulroy/skills/tree/main/tdd Command: npx skills add https://github.com/dmmulroy/skills --skill tdd-dmmulroy
It helps you build or fix TypeScript software by working test-first, so behavior is verified before implementation and regressions are caught early.
Use the tdd skill to plan and implement this feature test-first, starting with the most important public behavior.
High-intent search queries and answers about installing and using this skill.
To implement TypeScript features test-first, write integration-style tests against public interfaces, add one test at a time, write the minimum code to pass, then refactor safely after achieving green status. This incremental workflow verifies behavior before implementation and catches regressions early.
The red-green-refactor workflow in TypeScript testing involves writing a failing test, implementing the minimum code to make it pass, and then refactoring safely. It requires behavior-focused testing against public interfaces rather than coupling tests to internal implementation details.
Design integration tests for critical paths by testing against public interfaces, clarifying the expected behavior upfront, and prioritizing the most important public behaviors. This approach ensures evidence-driven validation and prevents regressions when building new features or fixing bugs.
Yes, you can use test-driven development for fixing bugs in TypeScript projects. Write a test that reproduces the bug against the public interface, implement the fix to reach green status, and refactor safely. This ensures the specific behavior is verified and prevents future regressions.
You should refactor code during a TDD workflow only after achieving green status, meaning all tests pass. This constraint ensures you have verifiable behavior coverage before modifying internal implementation, allowing safe refactoring without breaking existing functionality.
No, test-driven development here requires public-interface testing instead of coupling to internals. By writing integration-style tests against public behaviors, you maintain flexibility to refactor internal implementation details without breaking your test suite.
nguyennd93Automate test directory, configuration, and CI/CD setup for Node.js/TypeScript projects.
cill-i-amWrite failing tests before implementing minimal production code in a red-green-refactor workflow.
AndyHsuTWAutomate Django project verification with linters, security scanners, and tests.
drvossGenerate and parse coverage reports to locate uncovered lines and branches.
