Code Clarity

Optimize for the amount of code and state a maintainer must understand, not for the apparent completeness of each local branch.

Working method

1. Establish the real contract

Read the repository instructions and representative surrounding code before editing. State:

• the invariant that must remain true;
• the normal successful path;
• the failures that require different recovery behavior;
• the facts that are already authoritative;
• the requested scope and explicit non-goals.

Do not begin from the line mentioned in feedback. Begin from the abstraction that owns the behavior. A local complaint often reveals that the owner or invariant is wrong.

2. Inventory every proposed concept