Skill

refactor

Refactors code to simplify it without changing behavior. Use after features work to remove duplication, dead code, and unnecessary complexity while preserving contracts, tests, and build checks.

code-quality

npx claudepluginhub owainlewis/blueprint --plugin blueprint

Tool Access

This skill uses the workspace's default tool permissions.

Preview

- Simplifying code after behavior already works

SKILL.md

Similar Skills

code-simplifier

Refines existing code for clarity, readability, and maintainability without changing behavior, interfaces, or outputs. Use for simplify, clean up, refactor for readability requests.

amplify

simplify

147

Simplifies code by removing dead code, extracting duplicates (3+ repeats), and reducing nesting (>3 levels). Runs tests before/after to preserve behavior. Ideal wrap-up refactor.

6 tools

sd0x-dev-flow

code-simplification

27.2k

Simplifies code for clarity by reducing complexity while preserving exact behavior. Use when refactoring functional but hard-to-read code, during reviews, or for maintenance.

agent-skills

Stats

Stars79

Forks18

Last CommitApr 20, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Refactor

When to use

Simplifying code after behavior already works

Removing duplication, dead code, or unnecessary complexity

Cleaning up a focused area without changing what it does

Process

Choose the target from $ARGUMENTS, current changes, or a clearly relevant recent area. If there is still no clear target, ask.

Read the code and its surrounding context before changing it.

Remove dead code, flatten needless indirection, and simplify naming or structure where the behavior stays the same.

Run the relevant tests and build checks.

Verification

Behavior is unchanged

The code is simpler or smaller

Tests and build checks pass

Rules

Make the smallest safe refactor.

Preserve contracts and externally visible behavior.

Do not erase failure-path handling in the name of simplification.

If the goal is to change behavior, use a different skill.

If you are not sure a change is behavior-preserving, skip it.

Prefer deleting or simplifying over adding new abstraction.

If the code is already clean, say so.

Refactor

When to use

Simplifying code after behavior already works
Removing duplication, dead code, or unnecessary complexity
Cleaning up a focused area without changing what it does

Process

Choose the target from $ARGUMENTS, current changes, or a clearly relevant recent area. If there is still no clear target, ask.
Read the code and its surrounding context before changing it.
Remove dead code, flatten needless indirection, and simplify naming or structure where the behavior stays the same.
Run the relevant tests and build checks.

Verification

Behavior is unchanged
The code is simpler or smaller
Tests and build checks pass

Rules

Make the smallest safe refactor.
Preserve contracts and externally visible behavior.
Do not erase failure-path handling in the name of simplification.
If the goal is to change behavior, use a different skill.
If you are not sure a change is behavior-preserving, skip it.
Prefer deleting or simplifying over adding new abstraction.
If the code is already clean, say so.