Home Optibot Config Configuration Parameters for Optibot — Reviews

Configuration Parameters for Optibot — Reviews

Last updated on Apr 17, 2026

Configuration options for code reviews

The Reviews settings control automated code review functionality per repository. Access them from your Optibot dashboard at agents.getoptimal.ai → select a repository → Settings tab → Reviews section. All settings can be toggled from the form view or edited directly in the raw JSON panel.

Auto Review on PR Creation

Setting: Auto review Type: boolean Default: Off

Controls whether Optibot automatically reviews pull/merge requests when they are created.

When to use: Turn on if you want immediate feedback on all pull requests when they are first opened. Optibot will generate a full context-aware code review of your changes.

Turn off if you prefer to manually trigger reviews — you can always do this by typing Optibot can you review this in any PR or MR comment on GitHub or GitLab.

Auto Review on New Commits

Setting: Auto review on push Type: boolean Default: Off

Configures Optibot to automatically re-review a pull or merge request every time new commits are pushed. Gives you continuous feedback as you iterate on a PR without needing to manually request another review.

When to use:

  • Ideal when you push multiple follow-up commits to address feedback

  • Ensures each update is automatically re-reviewed

  • Removes the need to manually trigger additional reviews

  • Helps teams maintain high-quality, iterative review workflows

Auto Review After CI Workflow

Setting: Auto review after workflow Type: boolean Default: Off

Triggers a review only after a CI workflow completes rather than immediately on PR open. Useful if you want Optibot to review post-build, once you know the branch is in a stable state.

Automated PR Approvals

Setting: Allow approve Type: boolean Default: Off

Gives Optibot the ability to automatically approve pull/merge requests that pass its review criteria.

When to use:

  • For trusted contributors or automated dependency updates

  • When you have strict CI/CD checks and trust Optibot's judgment

  • When you regularly push atomic, small-to-medium PRs

  • When you require multiple approvals to merge — Optibot's approval can count as one

⚠️ Use carefully. This gives Optibot approval authority. Best combined with Excluded Labels or Excluded Users to maintain controlled auto-approval. Consider your team's review policies before enabling.

Recommended setup when using Allow Approve: Enable Auto Review, enable Allow Approve, and add excluded labels like needs-review and breaking-change, and excluded users for any junior engineers whose PRs should always require human review.

Code Suggestions

Setting: Code suggestions Type: boolean Default: On

Allows Optibot to generate inline code suggestions and improvements during reviews. Suggestions appear as committable changes or code change recommendations directly in the PR.

When to use:

  • Keep on for actionable, specific code improvement suggestions

  • Turn off if you only want high-level feedback without specific code changes — useful if your team has an internal mandate against AI-generated code suggestions, or if you're working to reduce engineer dependency on AI-generated fixes

Skip Files

Setting: Skip files Type: array of glob patterns Default: Empty

Tells Optibot to skip reviewing certain files based on glob patterns. Optibot will not generate suggestions on matching files and will not read them during a review.

When to use:

  • Exclude auto-generated files, test files, or documentation

  • Focus reviews on production code only and ignore compiled or built output

  • Skip files that change frequently or follow different conventions

  • Skip files with legal requirements against AI-generated code (some regulated industries require specific files to only be edited and maintained by humans)

Pattern examples:

Skip test files and documentation:

*.test.js, *.test.ts, *.md, docs/**/*

Skip generated and configuration files:

*.generated.*, dist/**/*, build/**/*, *.config.js, package-lock.json

Skip vendor and third-party code:

vendor/**/*, node_modules/**/*, third_party/**/*

Glob pattern reference:

  • *.ext — files with that extension in the repo root only

  • **/*.ext — files with that extension in any directory (recursive)

  • dir/**/* — all files under a specific directory

  • *.test.* — files with .test. in the name, repo root only

Review Sensitivity

Setting: Sensitivity Type: string — Low / Medium / High Default: Medium

Controls how aggressively Optibot flags issues in your code.

  • Low — Only reports high-confidence, critical issues such as bugs and security vulnerabilities. Best for teams that want a minimal, signal-only review with no noise.

  • Medium — The default. Balances critical findings with important improvements — covers bugs, security, and error handling without being overwhelming. Recommended for most teams.

  • High — Reports everything, including minor issues, stylistic concerns, and suggestions. Best for teams that want thorough, comprehensive feedback on every PR.

When to use:

  • Use Low if your team is getting too many comments and wants Optibot to focus only on what matters most

  • Use Medium for a balanced review experience (recommended)

  • Use High if you want maximum coverage and are comfortable triaging more comments per PR

Excluded Labels

Setting: Excluded labels Type: array of strings Default: Empty

Prevents Optibot from reviewing PRs or MRs that carry any of the specified labels. Labels are case-sensitive and must be an exact match.

When to use:

  • Skip reviews for work-in-progress changes

  • Skip auto-generated PRs from tools like Dependabot, Snyk, or SonarQube

  • Exclude draft or experimental branches

  • Bypass reviews for hotfixes or emergency changes

Examples:

Skip WIP and draft PRs:

WIP, work-in-progress, draft

Emergency bypass:

hotfix, emergency, critical-fix

Exclude documentation-only changes:

documentation, docs-only, readme-update

Note: Use exact label names as they appear in GitHub or GitLab — both platforms are case-sensitive.

Excluded Users

Setting: Excluded users Type: array of strings Default: Empty

Prevents Optibot from reviewing PRs or MRs opened by specified usernames. When a matching user opens a PR, Optibot will not review it even if Auto Review is on.

When to use:

  • Exclude dependency bots (Dependabot, Renovate)

  • Skip reviews for CI/CD and release automation accounts

  • Bypass automated deployment accounts

Examples:

Exclude dependency bots:

dependabot, renovate, renovate[bot]

Exclude CI/CD bots:

github-actions[bot], gitlab-ci, release-bot, deployment-bot

Note: Use the exact username as it appears on GitHub or GitLab, including any [bot] suffix where applicable.

Auto Review on Draft

Setting: Auto review on draft Type: boolean Default: Off

When turned on, Optibot will review pull or merge requests that are in draft state. By default, Optibot skips draft PRs and only reviews once the PR is marked "Ready to review" on GitHub (or equivalent on GitLab).

When to use: Turn on when you want Optibot to continuously review work-in-progress PRs as you build — useful for catching issues early before the PR is ready for human review.

Suppress Repeated Issues

Setting: Suppress repeated issues Type: boolean Default: Off

When enabled, issues that were already raised in a previous review on the same PR are moved to a collapsible section instead of being posted again as new inline comments. Reduces noise on PRs with multiple review cycles.

Note: All settings are per-repository. Configure each connected repository separately from the repository selector at the top of the Settings tab. Changes take effect immediately for new PRs and MRs — no commits or deployments required.