simplify_skill

Overview

This skill automates the Refactor phase of TDD: after tests pass, it refactors and simplifies code without changing behavior. It focuses on readability, maintainability, and consistency while ensuring the test suite stays green. Use it as a polishing step before a pull request or to remove technical debt after implementing features.

How this skill works

The skill runs the test suite to establish a safe baseline, then scans the target files or the repository for simplification opportunities like duplication, complex conditionals, or dead code. It applies small, incremental refactors and reruns tests after each change to ensure nothing broke. It avoids altering public APIs or adding functionality—only internal structure and clarity are changed.

When to use it

• Right after making tests pass with the /implement step
• Before opening a pull request to polish and standardize code
• When code is correct but hard to read or contains duplication
• To enforce project patterns and reduce technical debt
• Not for adding features or when tests are failing

Best practices

• Run the full test suite before and after each refactor to keep changes safe
• Make small, focused commits that each preserve passing tests
• Prefer extracting helpers and renaming for clarity over heavy redesign
• Avoid changing public APIs or adding speculative abstractions
• Follow existing project patterns and style conventions

Example use cases

• Extracting a repeated logic block into a descriptive helper function
• Renaming variables and functions to better reflect intent
• Removing obsolete code paths and unused imports
• Simplifying nested conditionals into clearer guard clauses
• Rewriting loops or comprehensions using more Pythonic idioms