improve-code-readability

What problem does it solve?

This skill helps teams identify and remediate structural issues that make code hard for humans to read, such as over-abstraction, tangled responsibilities, low locality of related logic, and unclear naming conventions.

Core Features & Use Cases

• Detect over-abstraction and deep call chains: identify call-depth hotspots, single-line wrapper functions, and layers that add little value.
• Improve locality and cohesion: recommend inlining, merging, or relocating logic so related behavior is visible in one place.
• Unify error handling and naming: standardize whether functions return errors or log them, and propose concise, intention-revealing names.
• Use case: audit a Go backend package where business flow is split across handlers, middleware, and tiny helpers, then produce prioritized, behavior-preserving refactor suggestions.

Quick Start

Analyze the target package and produce a prioritized list of specific refactor actions (inline, merge, rename, or unify error handling) with justification and test-preservation notes.