review-standard

To perform a code review for merge readiness, run a systematic three-phase process that evaluates documentation completeness, code quality, reuse of existing utilities, and advanced architectural concerns, resulting in a structured report detailing findings.

A standards-driven code review checks for documentation completeness, code quality, reuse of existing utilities, module focus, interface documentation, type safety, and architectural concerns to ensure changes meet project conventions before merge.

You can check code reuse and indirection by running a multi-phase review that systematically assesses whether new code leverages existing utilities and validates advanced architectural concerns against defined standards, providing feedback on merge readiness.

You need a multi-phase code review before merging new features to guarantee all new code is well-documented, adheres to project conventions, leverages existing utilities, and avoids common pitfalls like unnecessary indirection or type safety issues.

Yes, you can enforce project-specific conventions and type safety by validating code changes against defined standards during the advanced architectural phase of the review, ensuring interface documentation and module focus meet required criteria.

The best way to generate actionable refactoring feedback is to execute a comprehensive review that assesses code quality and architectural concerns, producing a structured report that details findings and recommendations for merge readiness.