How to Choose the Right Code Review Method

Decision guide for choosing the right code review method for architecture, implementation, testing, code quality, or refactoring.

Purpose

This page routes code-related work to the correct engineering review path. It is not a combined code-review procedure. Use it to choose whether the task belongs in architecture boundary review, standards-backed implementation review, test coverage and regression review, language/framework code-quality prompting, or behavior-preserving refactor planning.

When to use this

Use this section to decide whether this workflow is the right fit before you configure prompts, policies, or reference material.

  • Use case
    The review path is not clear yet
    Use this when the task is code-related but the main review question still needs to be classified before opening a guide or prompt.
  • Use case
    The task could fit more than one review type
    Use this when architecture, implementation correctness, testing, code quality, or refactor planning could be confused.
  • Use case
    You need to avoid a generic code-review request
    Use this before running a broad review so the work starts from the correct path and does not merge unrelated scopes.

Choose the correct engineering review path

Choose one path by the dominant engineering question. Open the matching procedure or prompt; do not merge paths unless the task explicitly asks for a multi-pass review.