← ClaudeAtlas

code-simplificationlisted

Simplify existing code while preserving its behavior and contracts. Use for requested refactoring; not read-only review or comment-only cleanup.
ValentinNikolaev/agent-skills · ★ 1 · AI & Automation · score 74
Install: claude install-skill ValentinNikolaev/agent-skills
# Code Simplification Remove unnecessary complexity while preserving observable behavior. Adapted from Addy Osmani's `code-simplification` workflow; see the bundled license and repository third-party notice. ## Route precisely - Use when the user asks to simplify or refactor working code without changing behavior. - Use `clean-code-comments` when only redundant comments should change. Use `code-review` for a read-only assessment of a diff and `review-arch` for system-level boundaries. - Do not broaden a feature or bug fix into unrelated cleanup merely because nearby code could be shorter. ## Understand before editing Read repository instructions, tests, callers, public contracts, and the reason for an apparent abstraction or branch. Note what must remain identical: API, serialized data, errors, side effects, ordering, concurrency, and user-visible behavior as applicable. Identify one concrete complexity cost, such as duplicated branching, indirection without a use, or a concept in the wrong owner. ## Simplify in bounded steps 1. Choose the smallest change that removes a concept, branch, or repeated decision. Prefer clarity over minimum line count, and follow local style. 2. Preserve boundary behavior. If a simplification requires changing a test's expected behavior, treat it as a behavior change and stop or obtain the appropriate scope. 3. Apply one coherent transformation at a time. Use repository tooling for mechanical changes that exceed safe manual review. 4. Run f