Review a code change for structural regressions that make code harder to change, delete, or reason about, including complexity moved rather than removed, missed simplifications, shared-path special cases, oversized files, wrong-layer logic, thin wrappers, premature abstraction, dead code, coupling, vague names, data-locality smells, stale comments, and type-safety holes. Use when reviewing for maintainability, simplicity, code structure, or design quality.
74
93%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Scanned
caafac3
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.