Install any skill in seconds. Free to start, no credit card required.
Get Started Free →sickn33/tdd-workflows-tdd-refactor
Use when working with tdd workflows tdd refactor
Passed 9 of 22 test cases with the skill, and 13 of 22 without it.
1 fixed8 passed either way13 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
A test case the skill fixed. Same model, same prompt, with and without the skill.
What verification checks must be satisfied on the safety checklist before committing refactored changes back to version control?
| Checked | Without skill | With skill |
|---|---|---|
| Verifies that all test suites pass with 100% green status. | Passed | Passed |
| Confirms that code coverage is maintained or improved relative to baseline. | 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 13 / 22 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.