Optibot Features — Optimal Docs

Optibot Features

Streamline your engineering workflow with Optibot, an AI-powered GitHub agent that reviews code, generates release notes, enforces compliance, bundles dependencies, and analyzes CI failures.

Most features run directly inside pull requests, so your team can focus on shipping, not manual reviews.

Code Review

Optibot automatically reviews your pull requests with context-aware analysis.

Push reviews get sharper with every commit — feedback focuses on your latest changes and the PR thread stays clean as you iterate.

Trigger manually in a PR comment:

#optibot review

Reviews your latest changes. For a complete review of the entire pull request:

#optibot full review

Or comment: Optibot, please review this PR

Dismiss Findings Outside the Diff

Some of Optibot’s most useful observations aren’t tied to a specific line — architectural notes, patterns spotted across the PR, broader code health signals. When one doesn’t apply to your situation, you can now dismiss it with a single click. Once dismissed, it won’t resurface on future reviews.

Release Notes

Turn technical updates into customer-ready release notes.

#optibot release notes

Compliance Checks

Automated SOC2 and security compliance scans directly in your PRs.

#optibot compliance

Dependency Bundler

Stop managing dozens of noisy Dependabot PRs.

Enable via .optibot configuration:

"dependencyBundler": { "enabled": true }

CI Fixer Agent

Debug CI failures automatically. The CI Fixer Agent detects failed workflows, analyzes logs, and automatically repairs code errors — restoring your build to green without manual intervention.

What it does

When a CI run fails, Optibot instantly posts an automated comment with the error details and affected files. The CI Fixer Agent then:

  1. Detects the failed CI run in a pull request
  2. Reviews the error logs and identifies affected files
  3. Applies targeted fixes directly to the branch
  4. Posts a PR comment summarizing the issue, changes, and context

Code Context, Search, and Judgment

Optibot is built on three foundations:

Code Context

Every review is grounded in your entire repository. Instead of treating a pull request as isolated text, Optibot considers dependencies, history, and team conventions.

Code Search

Optibot’s built-in search surfaces relevant references instantly, making it easy to see how similar challenges were solved and reducing duplicate work.

Judgment

Optibot applies reasoning to separate critical issues — like security risks or performance bottlenecks — from minor style concerns. Developers stay focused on what matters most.

Configuration File

Fine-tune Optibot using a .optibot file in your repo root:

{
  "reviews": {
    "auto": true,
    "autoApprove": true,
    "requestChanges": true,
    "excludedLabels": ["do not review"]
  },
  "dependencyBundler": { "enabled": true },
  "summary": { "auto": true, "level": "basic" },
  "guidelinesUrl": "https://github.com/your-org/your-guidelines.md",
  "enableCIFixer": true
}

Key Options

Option Description
reviews.auto Auto Reviews & Summaries — always-on reviews
reviews.autoApprove Auto-approve when all blockers resolve across pushes
reviews.requestChanges Submit formal GitHub “Request Changes” for blocking reviews (GitHub only, requires autoApprove)
reviews.excludedLabels Skip PRs with specific labels
guidelinesUrl Enforce company coding standards
dependencyBundler Consolidate dependency PRs
enableCIFixer Debug failed builds automatically

Why Optibot?

✅ Faster reviews

✅ Cleaner releases

✅ Built-in compliance

✅ Reduced PR clutter

✅ Smarter CI debugging

Optibot acts as your 24/7 AI reviewer, helping teams ship secure, reliable, and well-documented code.