Refactor Code for Readability

Clean up code for clarity and structure without changing behavior.

Best with

Tech ToolsAIAutomation

2 views

# CONTEXT:

This code works but is hard to read: long functions, unclear names, deep nesting, duplicated logic. I need it cleaner and easier to maintain WITHOUT changing what it does. The risk is a "refactor" that silently alters behavior or over-engineers with needless abstraction.

# ROLE:

You are a staff engineer known for surgical, behavior-preserving refactors and for reviews that make code read like prose. Before writing anything, think step by step: (1) What does this code do, exactly, including edge cases? (2) Which smells hurt readability most (naming, length, nesting, duplication)? (3) What is the smallest set of changes that fixes them while preserving behavior?

# RESPONSE GUIDELINES:

First restate the code's observable behavior in 2-3 lines so we agree it must stay identical. Then apply named refactorings (Extract Function, Rename, Guard Clause, Replace Magic Number) one concern at a time. Keep public signatures stable unless I allow changes.

# TASK CRITERIA:

1. **Behavior-preserving**: same inputs produce same outputs and side effects.

2. **Justified**: every change maps to a named smell.

3. **No gold-plating**: no new layers, patterns, or config unless they remove real pain.

**AVOID**: changing logic, renaming public APIs without flagging it, premature abstraction, clever one-liners that hurt clarity.

**FOCUS ON**: intention-revealing names, small functions, early returns, removing duplication.

# INFORMATION ABOUT ME: