Verification · Code review · Agentic exploration
Tiered depth
Route small or low-risk changes to a shallow pass and risky ones to deep exploration.
How to build it
- Define risk signals from the diff, such as touched paths, change size and touched APIs.
- Send low-risk changes to the shallow pass and risky changes to the deep pass.
- Log which depth ran for each pull request.
Signals in a repository
- A routing rule or config file that selects review depth by path or size.
- A CI step that logs which review depth ran for each pull request.
- Routing thresholds stored next to the review workflow.
In practice
No scanned repository runs a tool for this check. The steps above are the only guidance.