Review a pull request
Triggering a review from a PR comment
- On an open GitHub pull request or GitLab merge request, post a new comment:
/devin review. - Follow the link in Devin’s reply. Read the overview, then open a group of related changes to see how they fit together.
- In the Analysis sidebar or Bugs view, select a finding and check it against the code. If you need more context, quote it into chat. You can fix the code yourself or ask Devin to make an edit.
/devin review requests an analysis. A comment such as /devin fix the failing test asks a Devin session to do work on the PR instead. See Start Devin from a PR comment for GitHub and Start Devin from an MR comment for GitLab.
Other ways to open a review
- From Devin: Open Devin Review and choose a PR you authored, were assigned, or were asked to review. You can also paste a PR URL into the PR link field, including for GitHub Enterprise or Azure DevOps. You can omit
https://or useowner/repo#123for a GitHub.com PR. - From GitHub.com: Replace
github.comwithdevinreview.comin the PR URL. You can view a public PR without a Devin account. For a private PR, sign in with an account that has access. - From a Devin session: Select Analyze on the PR card. If the card offers both Analyze once and Analyze, choose Analyze once for a single review. Analyze also enables reviews on future pushes to this PR.
Cmd-click or Ctrl-click opens the PR in a new browser tab instead.
On the list, press j or k to select the next or previous PR, o or l to open it in the pane, or Enter to open its full review page. Where the PR allows it, a approves and advances to the next PR, and m merges or adds the PR to the queue and advances. These list shortcuts differ from the PR page shortcuts.
Devin Review in action
Reading a Review
Start with the overview to see what behavior the PR changes. In Guide view, read the diff by group: a group can bring together related edits from different files. When Devin detects copied or moved code, it shows the move rather than a deletion followed by an identical addition. Findings from the Bug Catcher appear in the Analysis sidebar or the Bugs view. Ask questions about the PR in the chat and get answers with relevant context from the rest of the codebase; you can also ask Devin directly from any comment, bug, or flag in the diff view. On mobile, the review opens on Changes. Switch to Bugs to see bugs, flags, and security findings, or use Description, Discussion, and Commits for the PR’s other details. When a link to a GitHub comment or review opens in Devin Review, it scrolls to and highlights the target. This also works in the review tab inside a Devin session, where a GitHub link to a file in the PR’s diff also opens at that file. When commits are pushed after the last review and no rule reviews them, a Devin hasn’t analyzed the latest changes banner names the last reviewed commit and how many commits are new. Analyze latest runs one more review of the current commit without turning auto-review on; Analyze automatically turns it on for this pull request, for all pull requests you open, or — if you can manage the repository’s Review settings — for every pull request in the repository. In the review tab inside a Devin session, See changes shows what was pushed since the last review. When a newer review becomes available, New commit switches to a commit pushed while the review was open, View latest commit switches to a newer diff for a commit Review already knew about, and New analysis updates the analysis without changing the displayed commit.Navigate Changes and Review History
- Mark files Viewed to track your progress, or mark all files viewed or unviewed from the file list.
- Expand context lines around a change, or use Expand all lines in a file’s header to show the whole file and Collapse expanded lines to fold it back. Switch a Markdown file between its rendered diff and source.
- Select lines on the new side of a diff to Add to Chat, or choose Suggest change to open a review comment on those lines prefilled with a suggestion block containing their current text.
- Hide whitespace-only changes to focus on substantive edits.
- The line counts in the PR header and on the Review list leave out tests and generated code by default. Hover over a count for its breakdown by category, and choose Relevant, Both, or Full there to change which count is shown. Clicking the count cycles through the same three displays. Your choice applies to both places.
- Press
Cmd+ForCtrl+Fto search the review. The filter icon in the find field offers Match case, Changed lines only, and Skip collapsed files. By default, search skips the contents of collapsed files, whether or not they are marked viewed. File and folder names still match. - Use Analysis history in the header actions menu to inspect an earlier analysis. In Select commits to view, you can reverse the order of reviewed commits. On GitHub, the picker also shows approvals and change requests tied to those commits. A link pinned to an older commit does not automatically show the newest results; use Switch to latest or Run analysis on latest when available.
- Check the Checks view for CI status. On providers that support it, manage reviewers, labels, and assignees without leaving Review.
- The diff settings menu has a Layout choice: File tree view shows ungrouped diffs with the file tree, and Guide view groups related changes with explanations.
Generated files and diff size limits
Files markedlinguist-generated in your Git repository’s root .gitattributes don’t count toward Devin Review’s diff size limit. Review shows their added and deleted line counts without analyzing the changes in those files.
Devin Review reads .gitattributes from the PR’s head commit, so a rule added in a PR applies to that PR’s review. Custom reviewers and Autoapprover only honor rules already on the merge base (the common ancestor used for the PR diff), so a PR can’t exclude its own files from them. For example, to mark files under src/generated/ as generated, add this rule to the root .gitattributes:
Bug Catcher
The Bug Catcher analyzes your PR for potential issues. Findings include Bugs, Flags, and Security. Beta custom reviewers have their own attributed findings. If a Devin session opened the PR to fix a code scan finding, the embedded review has a separate Finding or Findings tab for those linked findings. It appears in the Review or Inbox pane as well as the session’s PR tab, if you have access to the findings.Bugs
Devin marks likely errors as bugs. Investigate severe bugs first; they have a red bug icon. Less severe bugs have an orange warning icon. When available, expand Learn more for the failure scenario and recommended fix. The copy button includes the location, explanation, and any suggested edit.Flags
An Investigate flag raises a question about the code: check the flagged lines before deciding whether a fix is necessary. An Informational flag explains a change without asking you to fix it.Security
Devin Review scans for security vulnerabilities and displays them alongside other findings. Security scanning is part of a full review; use the posting settings to control whether security findings are posted as PR comments. A diff-only analysis, such as when automatic review is paused by a spending limit, is not a completed security review. The scanner checks for the following vulnerability categories:- Injection (SQL, XSS, command, template)
- Auth flaws (missing/broken access control, privilege escalation, auth bypass)
- Secrets exposure (hardcoded keys, tokens in logs, credentials in source)
- SSRF and path traversal
- Insecure deserialization, prototype pollution
- Missing input validation on untrusted data
- Weak cryptography (algorithms, key management)
- Transport/cookie security (missing HTTPS enforcement, permissive CORS, insecure cookie flags)
- Insecure defaults or misconfigurations introduced by the PR
- Critical — High-confidence vulnerabilities that should be fixed before merging
- Warning — Potential security weaknesses worth investigating
REVIEW.md to guide what the scanner looks for.
Where repository security-model context is available, the built-in review and custom reviewers marked Security-related also read SECURITY_MODEL.md, THREAT_MODEL.md, and threat- or security-model sections of SECURITY.md from the repository root.
What happens on the next push?
When Devin reviews a new push to a PR it has already reviewed, it usually looks for bugs introduced or affected by the changes since the last review. It carries earlier findings forward and checks whether the new commits fixed them. If the new commits substantially change what the PR does, or the new diff is too large for an incremental review, Devin can review the whole PR again. The per-PR auto-review spend limit applies across reviews, not separately to each push. Reaching that limit pauses future automatic reviews on the PR, not manual reviews.Review Comment Language
You can choose the language Devin Review uses for its comments and analysis from Settings > Preferences under the Devin Review section.- Follow display language (default) — Review comments follow your display language setting.
- A specific language — Choose a language from the Comment language dropdown to use it for review comments instead of your display language.
Acting on a Review
Resolving Findings
The Bugs tab lists findings by what is left to do with them:- Needs your attention — Open findings for you to triage.
- Devin is fixing — Findings the PR’s Devin session is working on. See Auto-Fix.
- Fixed — Findings closed as fixed by you or by Devin.
- Invalidated — Findings closed as not needing a fix, by you or by Devin.
Comments and Reviews
On GitHub, you can leave comments, approve the PR, or request changes from Devin Review. For other hosts, check the provider reference.Starting a review
When you write a top-level comment, a new inline comment, or a reply to an existing thread, the submit button offers two actions: Start a review batches your comments into a pending review instead of posting them individually, and Comment posts right away. Devin Review remembers the action you picked last and makes it the default, including for theCmd+Enter or Ctrl+Enter shortcut. Once a review is in progress, the button becomes Add to review and later comments join it until you submit. This is your review for the author, not a request for another Devin analysis.
Resolving comments
Resolve a discussion thread when you’ve addressed it. On GitHub, Devin minimizes a bot-authored review once all its threads are resolved, and shows it again if a thread reopens.Code owner indicators
A shield next to a reviewer in the sidebar means they were requested as a code owner.Code Changes from Chat
Ask the chat agent to make code edits. Review the suggested changes, then apply them as a commit to the PR branch without leaving Devin Review. This is different from Auto-Fix, which uses a Devin session to address findings.PR Workflow Actions
Devin Review lets you take action on PRs directly from the review page, without switching to GitHub.- Merge — Merge the PR with any merge method the repository allows (merge commit, squash, or rebase). When more than one is allowed, choose it from the merge button dropdown; Devin Review remembers your last choice for that repository and base branch in your browser. The merge button reflects the PR’s current mergeability status and required checks.
- Close — Close the PR without merging. Available from the dropdown menu next to the merge button.
- Convert to draft — Convert an open PR to draft status. Available from the dropdown menu when the PR is open and not already a draft.
- Mark ready for review — Mark a draft PR as ready for review. A “Ready for review” button appears in the merge bar for draft PRs; its menu also offers Review draft, which starts a review without marking the PR ready.
- Auto-merge — Enable or disable GitHub auto-merge from the merge button dropdown. When enabled, the PR will merge automatically once all required checks pass. The merge bar shows the current auto-merge status, including who enabled it.
Keyboard Shortcuts
m and n act immediately, like the buttons they stand for, so m merges without a confirmation. To change a binding, go to Settings > Keyboard shortcuts.
Stacked PRs
Devin Review treats stacked PRs as first-class. When a PR belongs to a stack, the review page shows the whole series and handles merging correctly:- Stack panel — The PR header shows the stack with every member ordered bottom-to-top, down to the base branch it merges into. Each member links to its own review page, so you can read the stack layer by layer. Reverse stack order next to the stack count lists the base branch first instead, and your choice is remembered.
- Per-layer readiness — Each member shows a status dot reflecting its true mergeability: green when it can actually merge (accounting for CI, required reviews, and branch protection), red for failing checks or conflicts, and orange for anything else blocking the merge — including when a layer is individually ready but blocked by an unmergeable PR below it. An aggregate indicator summarizes the whole stack.
- Focused diffs — Each PR in a stack is diffed against the layer below it, so every review — including auto-review and the Bug Catcher — sees only that layer’s change.
- Stack merge — Stacked PRs merge through GitHub’s atomic stack merge: merging a PR also merges every open PR below it in the stack, bottom-up, in a single operation. The merge button shows exactly how many PRs the action will land, and GitHub retargets the remaining PRs onto the base branch afterwards.
- Auto-merge — You can enable GitHub auto-merge on a stacked PR. When the stack is ready, GitHub lands the PR and every unmerged PR below it.
Commit & Comment Attribution
- Bug findings, flags, and automated annotations always appear as the Devin bot.
- When a user writes a comment or review through Devin Review, it appears under the user’s GitHub identity.
- When a user asks the chat agent to make a code change, the resulting commit is made as the Devin bot.
- GitHub Suggested Changes follow standard GitHub behavior: any reviewer (including Devin) can leave a suggested edit in a review comment. Applying a suggestion is separate from starting an Auto-Fix session.
- Devin will never create commits or comments on behalf of a user without the user explicitly initiating the action.
Auto-Fix
Auto-Fix uses a Devin session to address review findings on a PR. It is different from applying an individual suggested edit or asking the Review chat agent to prepare a commit.How to Enable It
For a PR already owned by a Devin session, Auto-Fix follows the Automatically fix Devin Review findings setting: “Devin will automatically triage the findings and decide whether to fix, validate, or escalate them to you.” It has an organization default and a personal choice:- For the organization — Organization admins turn it on or off in Settings > Devin under Pull requests. As the row says, “This option configures the default for all users.” Other members cannot change it. In an Enterprise account, each organization has its own default.
- For yourself — Turn it on or off for PRs from your own sessions in Settings > Preferences under Devin sessions. The switch shows the organization default until you change it. A choice that differs from the default shows a Reset to organization default pill, with an explanation on hover; click it, or flip the switch back to the organization’s value, to follow the organization again. Your own choice wins in either direction, including on over an organization whose default is off.
Auto-fix with Devin also turns Automatically fix Devin Review findings
on for you if it is off.
Findings on Devin’s own PRs
An eligible session that opened the PR takes new findings before they are posted individually. On GitHub:- The PR shows that Devin is fixing the findings, and they move to Devin is fixing in the Bugs tab.
- If Automatically fix Devin Review findings is on for the session owner and PR monitoring is active, the session fixes what it can and records a decision for each finding.
- Devin posts one review that says what it fixed, with the details under Fixed by Devin. Findings left for you are posted as review comments, following your posting settings. Findings Devin invalidated are not posted.
Permissions & Constraints
- Changing the organization default for Automatically fix Devin Review findings requires organization admin permissions. Each member’s own choice wins over the default for their sessions.
- Responding to bots in Settings > Devin > Pull requests still governs comments from other bots; it no longer controls Auto-Fix.
- Devin Review’s No Issues Found summary comments are always ignored. Only comments with actual findings trigger Auto-Fix.
If Automatically fix Devin Review findings is off when Devin Review posts findings, you’ll see a prompt in the session timeline to enable it.
Auto-Review
To review PRs you author, use your personal preferences. To review your team’s PRs, add a rule in Review settings. In either case, the repository must be connected to Devin, even if it is public.New accounts start with an account-wide rule that reviews PRs opened by Devin
sessions when they are ready and on every push, and Automatically fix Devin
Review findings is on by default, so those sessions fix the
findings. Edit or remove the rule in Review settings. Existing
non-Enterprise accounts with a single organization got the same rule and
setting, unless an admin had turned the setting off or removed the rule. In
every other existing organization the rules are unchanged, and the setting
is on only where Responding to bots already let Devin act on Devin
Review’s comments.
Trigger Modes
Choose when a rule starts:- PR is created — When the PR is opened, including as a draft.
- PR is ready — When the PR is opened ready or is marked ready.
- Only once — One review when the triggering conditions are met.
- Every push — Review again on subsequent pushes. This requires the full automatic-review usage tier. Where repository grants are used, a repository rule offers Every push if an organization that grants you edit access for that repository also permits Every push, even if you’re viewing Settings from another organization. See What happens on the next push? for what a follow-up review covers.
Self-Enrollment (All Users)
When personal enrollment is enabled for your account, users with a linked Git provider identity and the appropriate Review usage tier can enroll themselves without admin permissions.- Go to Settings > Preferences.
- Under Devin Review, set Analysis trigger to Analyze PRs automatically when opened or Analyze PRs automatically when ready for review.
- Set Analysis frequency to Only once or Every push, if your permissions allow it.
Scoped Rules and Exclusions
Review managers configure automatic review rules on the Review tab of Settings > Review. The page also has Security, Custom reviewers, Autoapprover, and Billing tabs; Security is shown to account Review managers. Open the add menu under Automatic analysis (Add repositories or users while the list is empty, Add repository afterwards) and choose what the rule covers: Add GitHub organization, Add GitLab group, Add Azure DevOps project, Add Bitbucket workspace, or Add Bitbucket project for every repository in that namespace; Add single repository for one repository; Add user for every PR an account member authors; or Add advanced rule to combine conditions. In the rule dialog, pick a Repository or Organization target, then narrow it with conditions:
is and is not compare the exact text; choose matches or does not match to use a glob pattern on repository, title, branch, and changed-file conditions. Then choose the rule’s starting event and cadence. The rule’s Analysis effort can use the account default or override it with Normal or Ultra.
For automatic rules with an Originated by Devin condition, the usage tier of the person who started the Devin session limits when that condition can match. A creation-only tier allows the first eligible review but not reviews on later pushes; a manual-only tier or no Review permission prevents the condition from matching.
Use exclusions for PRs the feature should not process. Matching exclusions take precedence over its enrollment rules.
When an exclusion stops auto-review on a PR, expand Automatic analysis skipped by an exception to see the matching rules you have access to. You can still run a one-off review; later pushes stay excluded.
Automatic review, each custom reviewer, and Autoapprover have separate rules. Enabling ordinary automatic review does not enable Autoapprover or a custom reviewer with no matching rule. An Autoapprover exclusion does not disable ordinary automatic review.
Rules replace the earlier repository and personal enrollment lists. Old legacy enrollment entries no longer launch reviews; configure the corresponding rules instead.
Under Git provider interaction, account Review managers can also turn off Let Devin Review edit the PR description (on by default), which adds a link and review status to the PR description. When it is off, your description is left untouched, and on GitHub the link and status appear in one PR comment instead.
Posting to GitHub
Account Review managers can configure what Devin posts back to the connected Git provider from Settings > Review. The Post findings to section, named after your connected providers, chooses which finding types are posted as comments: bugs and flags on the Review tab, and security findings on the Security tab. Git provider interaction on the Review tab holds the CI check and PR description link toggles:- Post CI check — When enabled (default), Devin creates a
Devin Reviewcommit status on supported providers for each review. Passing condition chooses when it passes: review completed (default), threads are resolved, or no findings. On Azure DevOps, the status is posted on the commit and on the pull request itself, so it shows in the pull request’s status list and can be required with a Status branch policy (genredevin, nameDevin Review). Set the policy’s Authorized identity to the account Devin posts with, so other identities can’t satisfy it. - Bugs — Post bugs (likely errors or incorrect behavior) as PR comments.
- Security — Post security vulnerabilities and hardening suggestions as PR comments.
- Flags (investigate) — Post investigate flags (potential issues worth a closer look) as PR comments.
- Flags (note) — Post informational flags (observations that may not require action) as PR comments.
Enterprise accounts: Settings apply across all organizations in the
enterprise. Account-wide posting controls require account-level Manage
Review; organization-level rule management does not grant permission to
change these defaults. An organization’s own Review settings page covers only
that organization’s repositories and locks the enterprise-wide settings,
marked Enterprise-level setting; change them from the enterprise’s Review
settings.
Instruction Files
Devin Review respects instruction files in your repository. If any of these files exist, they’ll be used as context when analyzing your PR:**/REVIEW.md**/AGENTS.md**/CLAUDE.md(case-insensitive)**/CONTRIBUTING.md(case-insensitive).cursorrules.windsurfrules.cursor/rules*.rules*.mdc.coderabbit.yaml/.coderabbit.ymlgreptile.json
.agents/, .devin/, agents/, .cursor/, .github/) are treated as belonging to the parent directory for scoping purposes. For example, src/.agents/REVIEW.md applies to files under src/.
These files supply context for a review. If you want a named check that reports its own findings, set up a custom reviewer instead.
REVIEW.md
REVIEW.md is a dedicated instruction file for Devin Review. Place it anywhere in your repository to customize how Devin reviews PRs in your project. Devin automatically picks up REVIEW.md files at any directory level (**/REVIEW.md), so you can scope review guidelines to specific subdirectories if needed.
Use REVIEW.md to define review-specific guidelines such as:
- Areas of the codebase that need extra scrutiny
- Common pitfalls or anti-patterns to watch for
- Project-specific conventions that reviewers should enforce
- Files or directories that can be safely ignored during review
- Security or performance considerations unique to your project
REVIEW.md:
Custom Review Rules
You can configure additional files to be read as review context from Settings > Review under Context. These file patterns are separate from custom reviewers: they supply background information rather than defining a reviewer that produces its own findings. To add repository files:- Find Context on the Review tab of Review settings.
- Select Add context. This opens Add repository files directly, or offers a menu where you can choose Repository files.
- Enter a file glob pattern, such as
docs/architecture/**/*.md, and add it.
Review-Context Instructions (Beta)
Written review-context instructions are in Beta and require beta access.
Repository instruction files remain available independently.
- Open Settings > Review and find Context.
- Open the add menu and choose Managed instructions, marked Beta.
- Enter a title and the review guidance.
- Choose All repositories or a narrower repository scope.
- Select Add context.
Custom Reviewers (Beta)
Custom reviewers are in Beta. If you can’t create or configure a reviewer, ask a Review manager for your organization or account.
Create a Reviewer
- Open Settings > Review and select the Custom reviewers tab.
- Select Add reviewer and enter a Name and optional description.
- Under Instructions, choose Plain text and describe what to check and what to ignore, or choose Repository skill or Organization skill (Enterprise skill in an enterprise) to drive from an existing skill.
- Choose Finding urgency: Severe for problems that must be fixed, Moderate for flags worth investigating, or Info for suggestions and context.
- Select Create and enable, or Save as draft to finish later.
- Open the reviewer and check Rules. If you can manage Review for the whole account, a new reviewer starts with Run with Devin Review on, so it joins every review. To limit it to certain PRs, turn this off and select Add reviewer rule. Otherwise, the reviewer starts with no rules, and you add one to select which PRs it checks.
Reuse a Skill
A reviewer created from a Repository skill, Organization skill, or Enterprise skill starts with Keep the reviewer in sync with the skill selected: its instructions are read-only in the reviewer and update as the skill changes. A repository skill is read from the repository’s default branch (usuallymain or master).
Repository skills are offered from the agent skill directories (such as .agents/skills/ or .devin/skills/) and from any plugin in the repository, using the directories its .devin-plugin/plugin.json or .claude-plugin/plugin.json lists in skills, or its skills/ directory by default.
If you clear the option, the reviewer keeps its current text and skill updates wait for your approval. To edit the instructions yourself, select Change source… and switch to Plain text, which unlinks the reviewer from its skill and keeps the current text.
In an enterprise, reviewers are shared. Text from one organization’s skill,
including its future edits, can only be read by members of that organization;
other Review managers can still edit the reviewer’s other settings.
Findings and CI Checks
Findings carry the reviewer’s name and configured urgency. View runs shows the run history for each reviewer with the count of fixed and ignored findings, and can filter runs by finding outcome. Each reviewer also has a CI check section. Its Post CI check setting chooses whether the reviewer’s findings count toward the Devin Review check (Part of Devin Review) or post a Separate check named after the reviewer, such asDevin Review / API compatibility. A separate check’s Passing condition can be:
- Reviewer finishes — completion is enough, even if it found issues.
- All comments are resolved — its posted comments have been resolved.
- There are no open findings — its findings are closed.
Spend Limit
Each reviewer’s Spend limit section controls what it can spend on automatic reviews of a single PR. Budget offers two options:- Part of Devin Review limit (default) — The reviewer’s spend counts toward the per-PR auto-review spend limit. Optionally set Limit per pull request to cap the reviewer below that limit.
- Separate budget — The reviewer spends from its own Limit per pull request, which is required, and keeps running after the Devin Review limit is reached. Only account-level Review managers can choose it.
Version History and Archiving
Select Last updated on … on the reviewer’s page to open its version history. It lists the 20 most recent versions of the instructions, each with what changed from the version before. Restore saves an earlier version’s instructions as a new version. A reviewer that follows a skill cannot restore an earlier version until it stops following the skill. Disable a reviewer to stop future runs while keeping its configuration. Archiving moves it to Archived reviewers below the reviewer list and stops its runs; findings it already posted are kept. Restore brings an archived reviewer back as disabled, so it does not run again until you enable it.Autoapprover (Beta)
Autoapprover is in Beta and requires beta access.
- Intent: Does the change match the PR author’s stated intent?
- Code quality: Does the change keep the codebase maintainable and easy to review?
- Incident risk: Could a problem in the change cause a reliability or security incident?
Set Up Autoapprover
- Open Settings > Review and select the Autoapprover tab. If the tab says Autoapprover is not available for your account yet, your account does not have beta access.
- Add an Autoapprover rule selecting the repository and PR conditions to evaluate.
- Optionally, add Autoapprover exclusions for PRs you never want it to evaluate.
Optional Custom Instructions
To tailor the default rubric, select Add instructions under Instructions and choose where they apply. Describe what your team is comfortable approving automatically and what always needs a person. For the criteria they address, these instructions take precedence over the default rubric; if instructions conflict, the narrower scope takes precedence. Autoapprover skips instructions it can’t verify, such as one that depends on CI status, and explains what it skipped in the verdict. When Autoapprover uses the rubric to evaluate a PR, it also readsAPPROVAL_POLICY.md files, and AUTOAPPROVE.md files (the earlier name), from the repository root and from the directories of the changed files and their parents. Autoapprover reads the files from the PR’s target branch, so a PR cannot write its own approval rules, and gives their text to the reviewer as instructions. A PR that changes an APPROVAL_POLICY.md or AUTOAPPROVE.md file always needs human review.
Instructions guide decisions but do not enroll PRs by themselves. For example, after adding a rule limited to a documentation repository, you could optionally add:
.github/ or diffs above a size limit. Keep branch protection and access controls in place.
Understand the Result
The PR’s Autoapprover section shows its result and reasoning:- Autoapproved — Devin approved the PR.
- Not autoapproved — the PR needs human review.
- Approved by a person — a human has supplied an approval.
Permissions and Cost
Permissions
Devin Review access is controlled by Devin Review permissions in the role editor. Usage tiers distinguish manual review, review on PR creation, and full automatic review. Account-wide configuration requires Manage Review (shown as Manage Devin Review in some role editors); a repository grant can be enough for the rules it covers, as described below. Enterprise admins can use Custom Roles to restrict usage or grant configuration access. Account-level permissions govern account-wide configuration; organization-level Review permissions govern access within enterprise organizations. Where repository grants are used, a grant to configure Review for a repository or Git connection can also give you access to Settings > Review for the rules it covers. Self-enrollment, where enabled, does not require Manage Review, but the available trigger modes are limited by your usage tier. See Account-level roles for the full list of Devin Review permission tiers and what each one grants. Managing an organization’s automatic review rules and exclusions requires the Manage analysis rules organization permission, which the built-in Review manager organization role grants on top of member permissions.Enterprise accounts: Organization Review managers can configure permitted
scopes without being primary-organization admins. Account-wide controls, such
as posting defaults and review-context instructions, still require account-level
Manage Review. Enterprise policy can prevent organization-level edits.
Cost control
Devin Review consumes ACUs (Agent Compute Units) from your enterprise’s ACU pool, the same pool used by Devin sessions and other Devin products. Enterprise admins have several tools to monitor and control review costs.Enterprise organization and consumption controls require a Devin
Enterprise account. Per-PR automatic review spending limits also apply
to quota-based plans. For enterprise plans, contact sales.
Consumption dashboard
The enterprise consumption dashboard at Settings > Consumption breaks down ACU usage by product, including a dedicated Review line in the daily consumption chart. Organization admins can view their org’s review consumption from Settings > Consumption Analytics. The dashboard includes:- Per-user breakdown — See how many review ACUs each user consumed in the current and previous billing cycle.
- Per-repository breakdown — See review ACU consumption, review count, and the number of bugs caught by repository for the current and previous billing cycle, helping identify which repos drive the most review cost and where reviews catch the most issues.
Review size indicator
Each PR in Devin Review displays a consumption pill showing the review’s t-shirt size based on total ACU usage across all review jobs on that PR:
Hover over the size pill to see the exact ACU total, the number of review jobs run, and the cost of the currently viewed review. This helps reviewers understand the cost impact of re-running reviews or enabling auto-review on high-churn PRs.
Per-PR auto-review spend limit
Admins can cap how much Devin Review spends on automatic reviews of a single PR from Settings > Review on the Billing tab, under Automatic analysis limits. The limit is measured in ACUs on ACU-based plans, or in dollars of on-demand spend on quota-based plans. Leaving the field empty uses the Cognition-managed default shown in settings; it does not mean unlimited. Once a PR’s total review spend across all of its review jobs reaches the limit, auto-review is turned off for that PR and future auto-reviews are skipped. Reaching the limit is a soft block:- Manual reviews still work — the limit only pauses automatic reviews. You can always trigger a review yourself from the PR review page.
- Re-enable per PR — Turning auto-review back on from the PR’s actions menu resumes reviews and adds another budget allowance. Recorded spend is not reset, and automatic reviews can pause again when the new budget is exhausted.
Review Effort and Billing Organization
Analysis effort in Review settings lets an account Review manager choose the default Normal or Ultra effort. Normal prioritizes price-performance; Ultra performs a more thorough review at a higher cost. Enterprise accounts also have a Default billing organization for automatic analysis setting on the Billing tab for reviews whose billing organization cannot otherwise be resolved. It requires account-settings permission. Where organization attribution is enabled, the review consumption display can show which organization, or the account itself, was billed for the most recent review. Where Repository billing rules are available on the Billing tab, organization Review managers can edit rules for delegated repositories and charge Review to an eligible organization or budget they manage. They can’t change a rule that already charges a payer they don’t manage.Supported Git Providers
dev.azure.com) and Azure DevOps Server 2020/2022. Connect through the Azure DevOps integration, a Microsoft Entra service principal, or an Azure DevOps Server collection with a personal access token, then enroll repositories from Settings > Review for auto-review. Devin posts automated findings through the connected service identity. To comment, reply, resolve threads, vote on a PR, or abandon a PR as yourself, link your personal Azure DevOps account to Devin. User-attributed actions require a supported delegated Microsoft identity; a shared server PAT does not supply one. Chat edits can be applied as a single commit, and linked accounts can list their PRs in Review. Merging, draft actions, and auto-merge are not available.
Bitbucket Data Center requires version 8.16 or later, connected through the Bitbucket integration. To comment, add or remove reviewers, approve, or decline a PR from Devin Review, link your Bitbucket account. Merging, labels, assignees, and reactions are not available, and code changes from chat are committed one file at a time.
Bitbucket Cloud (bitbucket.org) is supported through the Bitbucket integration. Connect your workspace with an access token or a dedicated Devin account linked with OAuth that administers the repositories (Devin installs the webhooks auto-review needs itself), then add automatic review rules from Settings > Review. Comments, replies, and declining a PR from Devin Review are posted as you, using your own Bitbucket account. Requesting reviewers, merging, draft actions, auto-merge, labels, assignees, and reactions are not available. Code changes from chat are committed in a single commit.
Perforce Swarm supports review analysis and automated findings through the connection’s service identity. The Devin Review UI is read-only for human comments and approval actions on this provider, and it cannot apply chat edits as commits. Swarm reviews do not appear in the personal PR inbox. Perforce connections are available to selected accounts.
