Choose a review policy for code or system design

Routing page for choosing the correct review policy for architecture, boundaries, or implementation against official sources.

Choose the correct code review policy

Use this page when the task is clearly code review, but you have not yet chosen whether the dominant problem is system structure or implementation correctness against official guidance.

Code Review: Architecture & Boundaries
Choose this when the dominant problem is structure, boundaries, ownership, or dependency flow.
Jump to Option 1 →
Code Review: Implementation vs Official Guidance
Choose this when the dominant problem is whether code or configuration is correct according to official guidance.
Jump to Option 2 →
Code Review: Test Coverage & Regression Risk
Choose this when the dominant problem is whether changed behavior is covered by tests and protected against regression.
Jump to Option 3 →

Routing rule

Do not treat this page as the normative contract for a concrete run. Choose the matching review path below and use the linked policy, procedure, or prompt as the active contract.

System structure
Choose Architecture & Boundaries
Use this when the main question is: “Is the system structure correct?”
This path is for structural diagnosis, ownership, and boundary correctness.
Implementation correctness
Choose Implementation vs Official Guidance
Use this when the main question is: “Is this implementation correct according to official guidance?”
This path is for framework, runtime, API, and source-backed implementation checks.
Testing impact
Choose Test Coverage & Regression Risk
Use this when the main question is: “Is the changed behavior covered by tests and protected against regression?”
This path is for missing test scenarios, coverage gaps, regression-sensitive behavior, and verification impact.

Choose the exact policy contract

Each option maps to one policy, one procedure, and the matching prompt files.

Option 1
Code Review: Architecture & Boundaries
Use this when the dominant question is about system structure, layering, dependency direction, boundary leakage, ownership, interface contracts, or minimal structural remediation.
This path is for architecture and boundary review, not for implementation-vs-docs checks.
Open policy
Procedure System prompt User prompt
Option 2
Code Review: Implementation vs Official Guidance
Use this when the dominant question is about code or config correctness, framework, library, runtime, or platform guidance, API misuse, version-sensitive implementation issues, or source-backed remediation.
This path is for implementation correctness against authoritative guidance.
Open policy
Procedure Prompt
Option 3
Code Review: Test Coverage & Regression Risk
Use this when the dominant question is whether changed behavior has enough test coverage, whether important scenarios are missing, or whether regression-sensitive behavior needs new verification.
This path is a public testing-impact review path inside the code-review policy. It does not require a separate policy page.
Open procedure
Prompt Chooser

Related libraries

Open the matching library when you need the broader policy set, adjacent procedures, or the linked prompt files.

Policies
Browse the broader policy library and adjacent review boundaries.
Open index →
How-to
Browse the procedural library and adjacent code-review workflows.
Open index →
Prompt library
Open the prompt files used by the code-review policy stack.
Open library →