clean-code

Start by identifying code smells such as long functions, unclear names, and duplicated logic. Then apply small, safe refactorings: extract functions that do one thing, rename variables to reveal intent, and add unit tests before changing behavior.

Base feedback on concrete principles rather than personal taste: flag functions doing more than one thing, non-searchable names, hidden side effects, and missing tests. Citing a principle like SRP or the Law of Demeter makes feedback objective and actionable.

Functions should be small, do exactly one thing, and operate at a single level of abstraction. Keep arguments to zero or one where possible, avoid side effects on global state, and use descriptive verb-based names like postPayment.

Prefer expressing intent in code over comments; most comments signal unclear code. Reserve comments for legal notices, clarifying external library behavior, explaining regex intent, and TODOs, and avoid redundant or misleading commentary.

These principles are guidelines, not substitutes for environment-specific validation, testing, or expert review. Rules like maximum function length or argument counts require judgment, and strict application may not fit every codebase or performance constraint.