Code Review — choose the correct review path

Routing page for code review workflows. Choose architecture & boundaries or implementation vs official guidance.

Purpose

Use this page when the task is clearly code review, but you still need to choose the correct review path.

Do not start with a generic all-purpose code-review prompt. Choose the dominant review type first, then run the matching procedure.

Option 1 — Code Review: Architecture & Boundaries

Choose this when the main question is about:

  • system structure,
  • module/layer boundaries,
  • dependency direction,
  • ownership,
  • interface misuse,
  • state leakage,
  • minimal structural remediation.

Open:

Option 2 — Code Review: Implementation vs Official Guidance

Choose this when the main question is about:

  • whether code or config changes are correct,
  • framework/library/runtime/platform guidance,
  • API misuse,
  • version-sensitive implementation issues,
  • source-backed remediation.

Open:

Quick decision rule

  • If the question is “Is the system structure correct?”, choose Code Review: Architecture & Boundaries.
  • If the question is “Is this implementation correct according to official guidance?”, choose Code Review: Implementation vs Official Guidance.
  • If you need both, run them separately, in this order:
    1. Code Review: Architecture & Boundaries
    2. Code Review: Implementation vs Official Guidance

Common mistakes

  • Starting with implementation guidance when the real problem is structural.
  • Treating architecture review as if it were code-style or framework-guidance review.
  • Mixing both review types into one run by default.
  • Looking for a single mega-prompt called “code review” instead of choosing the correct path.