representation-envy-refactor

Representation envy occurs when code improperly accesses or manipulates another object's internal state. This Skill detects such method and variable interactions during code reviews and suggests moving behavior to the object that owns the representation.

To improve object ownership, analyze your codebase to identify where methods improperly depend on another object's internal state. This Skill suggests refactoring guidance to move that behavior directly to the object that owns the representation.

You identify code accessing another object's internal state by analyzing method and variable interactions across your codebase. This Skill automates this detection process to highlight cases where a class improperly depends on external internal state.

Yes, this code analysis approach applies directly to code reviews and refactoring processes. It analyzes method and variable interactions to identify representation envy and suggest improvements for better object design and encapsulation.

You should avoid representation envy refactoring when method and variable interactions do not involve improperly accessing another object's internal state. If object ownership and encapsulation are already correct, this refactoring approach offers no value.