Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →dokhacgiakhoa/tdd-workflows-tdd-refactor
Use when working with tdd workflows tdd refactor
Passed 8 of 15 test cases with the skill, and 7 of 15 without it.
and 1 more in the full report
3 fixed8 passed either way9 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are about to refactor a legacy C++ inventory allocation module that has no recorded performance numbers or baseline test logs. What is the very first action to take before modifying any code files?
| Checked | Without skill | With skill |
|---|---|---|
| Specifies running existing tests to establish a green baseline before modifying any code. | Missed | Passed |
The instructions your model reads when the skill loads.
resources/implementation-playbook.md.Refactor code with confidence using comprehensive test safety net:
[Extended thinking: This tool uses the tdd-orchestrator agent (opus model) for sophisticated refactoring while maintaining all tests green. It applies design patterns, improves code quality, and optimizes performance with the safety of comprehensive test coverage.]
Use Task tool with subagent_type="tdd-orchestrator" to perform safe refactoring.
Prompt: "Refactor this code while keeping all tests green: $ARGUMENTS. Apply TDD refactor phase:
1. Pre-Assessment
2. Code Smell Detection
test cases passed, vs 7 / 15 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.