Review depth
Review depth sets how much investigation goes into a review. Standard suits most pull requests; Deep spends more time and credits on complex or sensitive changes.
Standard and Deep
| Depth | What HeyDeer does | Suited to |
|---|---|---|
| Standard (default) | Reviews the change from independent perspectives and verifies each finding against the code. | Most pull requests |
| Deep | Also looks beyond the immediate diff and cross-checks potential regressions. Usually takes longer. | Refactors, and changes to payments, authentication, or other sensitive code |
Deep uses more credits than Standard, because cost follows the work a review needs. See How credits work.
Default review depth
Set Default review depth in Organization settings → Review rules, under How to review, or per repository; see How settings work. Automatic reviews, PR comment commands, and the Review this revision button use it.
To use another depth once, choose New review on the Reviews page in HeyDeer and pick Standard or Deep under Review depth.
A common setup keeps Standard as the organization default, sets Deep on repositories with sensitive code, and starts a one-off Deep review for a risky pull request.
Deep reviews and repository checks
In a Deep review, HeyDeer spends extra effort on each matching repository check. For a simple check, such as a naming rule, add skip_extra_reviewers: true to its frontmatter so Deep reviews handle it as Standard would. Leave it off for checks that guard risky behavior.
---
files: "src/**/*.ts"
skip_extra_reviewers: true
---
Exported functions use camelCase names.
Report any exported function that does not.