review

PR review orchestration works by reading a concern registry and applying routing rules to your code changes. It executes seven phases covering classification, routing, reviewer selection, and execution to ensure comprehensive coverage.

A concern registry routes PR reviewers by applying predefined routing rules to classify diverse change classes. It activates concerns based on risk signals and selects appropriate reviewers for parallel execution across security, correctness, and other always-on areas.

An automated PR review workflow enforces structured outputs including activated_concerns, activation_reason, risk_signals, likely_one_way_doors, reviewers_to_run, and coverage_confidence. These provide transparent reasoning for every review decision.

Yes, you need design docs and routing tables in your repository, specifically located at docs/design/CONCERNS.md. The PR review workflow depends on these files to read the concern registry and apply the correct routing rules.

Yes, you can automate reviewer dispatch for security, correctness, and other always-on concerns. The PR review workflow handles this by routing concerns and executing selected reviewers in parallel based on your change classification.

To assess one-way door risks in a pull request, use a structured review workflow that identifies risk signals and likely_one_way_doors. It evaluates these risks during the classification phase to guide reviewer selection and execution.