Feedback scope
Feedback scope decides which findings HeyDeer reports, based on confidence and severity. Serious findings can be reported with less certainty, and Low-severity findings, which don’t need to hold a merge, can be left out. It filters what HeyDeer posts, not what it reviews or what the review costs.
The three scopes
Severity (Critical, High, Medium or Low) is a finding’s impact if it’s real. Confidence is how sure HeyDeer is that it exists. Each scope sets the minimum confidence for each severity:
| Scope | Critical | High | Medium | Low |
|---|---|---|---|---|
| Concise | Likely | Certain | Certain | Certain, from repository checks only |
| Balanced (default) | Suspected | Likely | Certain | Certain |
| Detailed | Suspected | Suspected | Likely | Likely |
Certain means a complete evidence chain with no important unresolved premise. Likely means strong evidence with a small unresolved assumption. Suspected means a concrete code basis with an important unverified premise. These are evidence judgments, not measured probabilities.
A repository check states what your team wants raised, so no scope leaves out its findings for their severity. Concise suits teams that read every comment; Detailed suits teams whose coding agent verifies each finding before fixing it.
Findings outside your feedback scope are ignored: they are not reported, do not fail the check, and do not block automatic approval.
Set and preview the scope
Set Feedback scope in Workspace settings → Review rules, under How to review, or in a repository’s Review rules; see How settings work. To use another scope once, choose it in Start a review.
To compare scopes, open a completed review in HeyDeer. When another scope would keep different findings, choose it beside Findings, or select Preview under a result without findings. Previewing changes nothing on GitHub or in your settings.
Start with Balanced, and preview other scopes on recent reviews before switching. A narrower scope hides findings but doesn’t fix their cause; see Reducing noise.