Skip to main content
Diagnose Code Review from the outside in: provider access → repository sync → repository enablement → trigger → context → output. This order finds the broken layer without changing unrelated settings.

​
Fast diagnostic

1

Confirm provider access

Verify that the Git integration can see the repository and pull request.
2

Confirm repository sync

Check Settings → Code Management, then locate the repository under Code Review → Codebases.
3

Confirm review enablement

Open Show details and verify PR Review is enabled.
4

Request an explicit review

Comment @entelligence review on a non-draft pull request. This separates trigger problems from review-engine problems.
5

Inspect context and output

If the review runs but looks wrong, check guidelines, Learnings, Markdown context, linked codebases, exclusions, priority, and comment style.
Code Review repository diagnostics with sample metrics and repositories awaiting scan data

​
Common problems

​
Permission model

Code Review needs read access to repository and pull-request content. Posting reviews, replying, resolving threads, submitting approvals, linking tickets, and creating changes require the corresponding write capability. Your Git provider remains the authority for branch protection, required checks, merge rules, and repository membership. Entelligence approval does not merge a pull request.

​
Reduce impact while investigating

  • Disable Auto Review on Every Commit to stop repeated runs.
  • Disable PR Review for the affected repository to pause automation.
  • Restore the recorded previous guideline, Learning, linked codebase, exclusion, or output setting.
  • Revoke provider access only when the integration must stop immediately.
  • Identify dependent clients before deleting or rotating credentials.

​
Send support a useful report

Include:
  • Workspace and repository
  • Git provider
  • Pull-request URL and commit SHA
  • UTC timestamp and local timezone
  • Expected trigger and current repository setting
  • Exact visible error text
  • Whether @entelligence review reproduces the issue
  • Screenshots with secrets and unrelated private data removed
Never send access tokens, API keys, private source, or raw credentials through an unapproved channel.

​
Next step

Return to the Code Review quickstart after the connector or setting is corrected.