Anatomy of a finding
Review the cited code and surrounding context before applying a suggestion. A good suggestion shortens the fix; it does not remove the need to verify behavior and tests.
Review output
Priority controls
Each repository can choose how much feedback is posted:- Critical issues only keeps the review focused on the highest-priority problems.
- Medium priority and above balances coverage with comment volume.
- All issues includes lower-priority and nitpick-level feedback.
Confidence score
When Show Confidence Score is enabled, the summary includes a score from 1 to 5. It reflects the findings Entelligence evaluated and whether they remain unresolved. Auto-approve at 5/5 can submit a Git-provider approval. It never merges the pull request or bypasses required checks.Respond to a finding
1
Inspect the evidence
Read the affected code, related call sites, and the repository rule behind the finding.
2
Ask for clarification
Reply directly to the Entelligence thread when the reasoning is incomplete. No extra mention is required in the bot’s own thread.
3
Fix or teach
Apply a reviewed suggestion when the issue is valid. If the finding is a recurring false positive, provide negative feedback so it can become a scoped Learning.
4
Verify and resolve
Run the relevant tests, confirm the behavior, and resolve the thread after the issue or misunderstanding is addressed.