pragmatic-architect

Code architecture review evaluates file boundaries, naming conventions, and dependencies to ensure responsibilities stay separated. It flags vague names, duplicate logic, and hidden dependencies to keep coupling low and changes safe.

Refactoring existing code while preserving behavior requires identifying the smallest useful change set. It separates concerns, keeps modifications minimal and testable, and maintains consistency with existing project style to avoid unintended side effects.

Improving code maintainability during feature additions involves reviewing naming hygiene, removing noisy comments, and avoiding premature abstractions. It keeps changes minimal, testable, and consistent with project style to prevent unnecessary complexity.

Architecture review applies to small bug fixes, large greenfield builds, and existing codebase modifications. It provides practical guardrails for file boundaries and naming conventions across varying task sizes while ensuring changes remain testable.

You should avoid adding new abstractions during a code refactor when they do not yet earn their keep. Architecture review flags unnecessary complexity, recommending minimal change sets that preserve behavior and maintain clear boundaries.