Apply review fixes without leaving GitHub.

Ask Optibot to apply any fix it flagged in a code review and it commits the change back to your branch — with full codebase context, a summary of what changed, and zero back-and-forth. The gap between review comment and fixed code closes in seconds.

How does the Review Fixer Agent work?

1. Optibot reviews the PR and flags issues
   Optibot reviews the pull request and posts inline comments on every flagged line — bugs, logic gaps, code quality issues, security concerns, and improvement suggestions. Each comment includes Optibot's reasoning and a suggested approach to resolving the issue.

2. Engineer asks Optibot to apply a fix
   The engineer reads the review and decides which issues to address. For any comment they want Optibot to act on, they reply directly in the PR — naturally, like asking a teammate: "Optibot apply this fix," "Optibot fix this," or "Optibot what’s the best approach here?" No commands, no configuration, no leaving GitHub.

3. Agent applies the fix with full codebase context
   The Review Fixer Agent reads the flagged issue, the review comment, and the full codebase context — your repo's patterns, types, existing architecture, and related files. It generates a targeted fix and commits it directly to the PR branch. The fix is codebase-aware, not a naive patch — it understands how the change fits into the rest of your code.

4. Fix is committed and logged
   Optibot posts a PR comment summarizing what was changed, what files were touched, and why — with a commit link. The fix appears immediately in the PR diff for human reviewers to inspect and approve. All fixes applied by the Review Fixer Agent are also logged in the dedicated Fixes page in your Optibot dashboard, giving your team a complete record of every agent-applied change.

From review comment to committed fix in seconds.

The Review Fixer Agent closes the loop between code review and code change — no manual editing, no context switching, one click to enable.

What does the Review Fixer Agent do?

Six capabilities that activate the moment you enable the agent.

• Full codebase context on every fix
  Fixes aren't generated from the diff alone. The agent reads your repo's types, imports, patterns, and architecture — so the committed code fits your codebase instead of breaking something three files away.

• Natural language triggers
  Ask Optibot to apply a fix the same way you'd ask a teammate. Reply to any review comment in a PR and the agent picks up the request instantly — no slash commands, no configuration, no learning curve.

• Targeted commits, not rewrites
  The agent touches only what the review comment flagged. No scope creep, no reformatting unrelated lines, no surprise changes in the diff. The fix is surgical — reviewers see exactly what changed and why.

• PR comment summaries on every fix
  Every applied fix is documented with a PR comment explaining what was changed, which files were touched, and the reasoning behind the approach. Reviewers get the full narrative without hunting through the diff.

• Fixes dashboard — full visibility
  Every fix applied by the Review Fixer Agent appears in the Fixes page in your Optibot dashboard. See a complete history of agent-applied changes across all repositories — what was fixed, when, which PR, and which review comment triggered it. Full audit trail, one place.

• Engineer stays in control
  The Review Fixer Agent never applies fixes automatically. It only acts when an engineer explicitly asks it to — on the specific comment they choose. Human approval of the PR remains unchanged. The agent does the implementation work; the engineer makes the decisions.

How do I enable the Review Fixer Agent?

Toggle on from your Optibot settings dashboard — no config files, no pipeline changes. The agent activates on your next PR review.

Review Fixer vs. CI Fixer — what's the difference?

Review Fixer Agent

• Fixes code quality and logic issues found during Optibot's PR review
• Human-initiated — engineer asks Optibot to apply a specific fix
• Triggered by a PR comment — "Optibot apply this fix"
• Applies fixes with full codebase context
• All fixes tracked in the Fixes dashboard

CI Fixer Agent

• Fixes failed CI builds — type errors, syntax issues, broken imports
• Automatically triggered — runs the moment a workflow goes red
• No human input required to trigger a fix
• Applies fixes directly to the branch and re-runs CI
• Fix summary posted as a PR comment

Both agents are available from the same Agents settings panel and can be enabled independently.

Frequently Asked Questions

• How is the Review Fixer different from Copilot or Cursor suggesting fixes?
  Other tools suggest fixes inline in your editor and require the engineer to manually apply, test, and commit them. The Review Fixer Agent applies the fix directly to the branch, commits it back to the PR, and documents what changed — all from a GitHub PR comment.

• Does the Review Fixer Agent apply fixes automatically?
  No. The agent only acts when an engineer explicitly asks it to in a PR comment. It never applies fixes without being prompted. This keeps engineers in control of every change — the agent does the implementation work, the engineer makes the decisions.

• How does it avoid breaking other parts of the codebase?
  The agent generates fixes with full codebase context — it reads your repo's types, imports, patterns, and related files before writing the fix. It doesn't patch in isolation. The fix is designed to fit your existing architecture, not just solve the immediate issue.

• Where do I see all the fixes the agent has applied?
  Every fix is logged in the Fixes page in your Optibot dashboard. You can see a complete history of agent-applied changes across all repositories — what was fixed, when, which PR triggered it, and which review comment was the source.

• Can I use the Review Fixer and CI Fixer at the same time?
  Yes. Both agents can be enabled independently from the same Agents settings panel. They solve different problems — the Review Fixer handles code quality and logic issues from PR reviews, the CI Fixer handles failed builds.