Claude Code Plugins

Community-maintained marketplace

Feedback

tdd-refactor-phase

@rubrical-studios/idpf-praxis-dist
0
0

Guide experienced developers through REFACTOR phase of TDD cycle - improving code quality while maintaining green tests

Install Skill

1Download skill
2Enable skills in Claude

Open claude.ai/settings/capabilities and find the "Skills" section

3Upload to Claude

Click "Upload skill" and select the downloaded ZIP file

Note: Please verify skill by going through its instructions before using it.

SKILL.md

name tdd-refactor-phase
description Guide experienced developers through REFACTOR phase of TDD cycle - improving code quality while maintaining green tests
license Complete terms in LICENSE.txt

TDD REFACTOR Phase

Version: v0.18.0

Guide through REFACTOR phase: improving code quality while keeping tests green.

When to Use

  • GREEN phase complete with passing test
  • User responds "Done-Next-Step" after GREEN phase
  • Code works but could be improved

Objectives

  1. Improve code quality - Cleaner, more maintainable
  2. Keep tests green - No behavior changes

Refactoring IS: Improving structure without changing behavior Refactoring IS NOT: Adding features, fixing bugs, breaking tests

Workflow

Step 1: Analyze Opportunities ASSISTANT instructs: "Ask Claude Code: Analyze this code for refactoring opportunities" Identify: Duplication, long functions, unclear names, complex logic

Step 2: Evaluate Suggestions

  • Refactor Now: Clear improvement, low risk, high value
  • Skip: Premature abstraction, high risk, over-engineering

Step 3: Apply Refactoring (Single Code Block)

TASK: [Description]
STEP 1: Open implementation file
STEP 2: Navigate to code
STEP 3: Apply refactored code
STEP 4: Explanation of improvements
STEP 5: Save file
STEP 6: Run full test suite
STEP 7: Verify ALL tests still PASS
STEP 8: Report: All tests green?

Step 4: Verify Tests Remain Green

  • Run FULL test suite
  • ALL tests must pass
  • If any fail → ROLLBACK immediately

Step 5: Complete

  • Refactoring applied + tests green → "Done-Next-Step"
  • Refactoring skipped → "Done-Next-Step"

Best Practices

  1. Refactor in small steps (test after each)
  2. One refactoring at a time
  3. Keep tests green (rollback if broken)
  4. Refactor for clarity, not cleverness

Common Refactorings

  • Extract Variable/Function
  • Rename for Clarity
  • Eliminate Duplication
  • Simplify Conditional Logic

When to Skip

  • Only one use of code (Rule of Three)
  • Code already clear
  • High risk, low value
  • Premature abstraction

Anti-Patterns

  • Refactoring without tests
  • Accepting broken tests
  • Big bang refactoring
  • Mixing refactor + features

Checklist

  • Claude Code analyzed code
  • ASSISTANT evaluated suggestions
  • If applied: All tests PASS
  • If skipped: Valid reason documented
  • User reported via "Done-Next-Step"

End of TDD REFACTOR Phase Skill