Fix It For Me: How Macroscope Automatically Fixes Bugs in Pull Requests
Fix It For Me is Macroscope's AI code fixer that automatically creates branches, implements fixes, opens pull requests, and iterates until CI passes. Not just review — actual automated bug fixes.
Fix It For Me is Macroscope's AI code fixer that goes beyond review comments. When Macroscope's AI code review detects a bug in your GitHub pull request, Fix It For Me automatically creates a new branch, implements the fix, opens a pull request, runs your CI checks, and iterates on failures until the fix passes. It turns AI code review findings into working code — not just suggestions.
TL;DR — What is Fix It For Me?
- What: An AI code fixer built into Macroscope that automatically fixes bugs found during code review
- How: Creates a branch from your feature branch, commits the fix, opens a PR, runs CI, and retries if tests fail
- Trigger: Reply to any Macroscope review comment with "fix it for me" on GitHub, or ask @Macroscope in Slack
- Auto-merge: Optionally auto-merges the fix PR when CI passes
- Cost: Included with Macroscope's usage-based pricing — no extra fee
- Limitation: Not available on cross-repo or fork pull requests
What Is Fix It For Me?
Fix It For Me is an AI code fixer that automatically resolves bugs detected during Macroscope's AI code review. Most AI code review tools stop at comments — they tell you what's wrong and leave you to fix it. Fix It For Me closes the loop. It takes the bug Macroscope found, creates a new branch, writes the fix, opens a pull request, and validates the fix against your CI pipeline.
Fix It For Me is part of Macroscope's AI code review platform, which automatically reviews every GitHub pull request for runtime bugs, logic errors, and regressions. When the review finds an issue, Fix It For Me gives you a one-click path from "here's a bug" to "here's a working fix, ready to merge."
This makes Macroscope both an AI code reviewer and an AI code fixer — the only GitHub code review tool that detects bugs and ships fixes in one integrated workflow.
How Does Fix It For Me Work?
Fix It For Me follows a five-step automated workflow:
Step 1: Create a Fix Branch
When you trigger Fix It For Me, Macroscope creates a new branch from your feature branch (on GitHub) or from your main branch (when triggered from Slack). All fix branches follow the macroscope/*/** naming pattern so they're easy to identify and manage.
Step 2: Implement the Fix
Macroscope's AI code fixer analyzes the bug it detected, understands the surrounding code context using its AST-based codebase graph, and writes a fix. The fix is committed to the new branch.
Step 3: Open a Pull Request
Macroscope automatically opens a pull request for the fix. The PR includes a description of what was fixed and why, linking back to the original review comment.
Step 4: Run CI and Iterate
This is where Fix It For Me separates from every other AI code fixer on the market. Your existing GitHub Actions run against the fix branch. If CI fails, Macroscope reads the failure logs, diagnoses the problem, and commits another fix attempt. This iterate-until-green loop continues until the fix passes your test suite.
Other AI code fixers suggest a diff and hope it works. Fix It For Me validates the fix against your actual CI pipeline and iterates until it does.
Step 5: Auto-Merge (Optional)
If auto-merge is enabled, Macroscope merges the fix PR once CI passes. You can control this per request:
- "Fix it for me and auto-merge" — Forces merge on successful checks, regardless of default settings
- "Fix it but don't auto-merge" — Leaves the PR open for manual review
When auto-merge can't proceed (e.g., branch protection conflicts), Macroscope posts an explanatory comment. Note: PRs against main always require manual merge regardless of auto-merge settings.
How Do You Trigger Fix It For Me?
Fix It For Me can be triggered in two ways:
On GitHub: Reply to any Macroscope review comment on your pull request. Ask it to fix the issue. Macroscope reads the context of the review comment, the surrounding code, and creates a fix branch.
On Slack: Direct the @Macroscope bot to fix a bug or implement a change. Macroscope creates a branch from main, implements the change, and opens a PR.
Both paths result in the same automated workflow: branch, fix, PR, CI loop, optional merge.
Why Is Fix It For Me Different from Other AI Code Fixers?
The AI code fixer market is growing. Sonar has AI CodeFix. DeepSource has Autofix. Sentry has AI-powered Autofix for production errors. GitHub Copilot suggests inline fixes. But Fix It For Me operates in a fundamentally different way.
Fix It For Me vs. Sonar AI CodeFix
| Fix It For Me | Sonar AI CodeFix | |
|---|---|---|
| What it fixes | Runtime bugs, logic errors, regressions found in PR review | Static analysis issues (code smells, vulnerabilities) |
| Output | Full branch + PR + CI validation loop | Suggested diff in the Sonar UI |
| CI integration | Runs your tests, iterates on failures | No CI loop — suggestion only |
| Context | Full codebase graph (AST-based cross-file analysis) | Single-file static analysis |
| Trigger | During GitHub PR review or via Slack | In Sonar dashboard after scan |
Sonar AI CodeFix suggests fixes for static analysis findings. Fix It For Me fixes runtime bugs found during deep code review and validates them against your actual test suite.
Fix It For Me vs. DeepSource Autofix
| Fix It For Me | DeepSource Autofix | |
|---|---|---|
| Fix delivery | Opens a PR with full CI validation | Single-click diff application |
| Iteration | Retries if CI fails | No retry — one-shot fix |
| Bug detection | AST-based cross-file analysis | Pattern-based static analysis |
| Auto-merge | Yes, configurable per fix | No |
DeepSource Autofix generates fixes for issues flagged by its static analysis engine. Fix It For Me generates fixes for deeper bugs — the kind that require understanding how multiple files interact — and validates them end-to-end.
Fix It For Me vs. Sentry Autofix
| Fix It For Me | Sentry Autofix | |
|---|---|---|
| When it runs | During PR review (before merge) | After production errors (after merge) |
| Bug source | Code review findings | Production error traces |
| Context | PR diff + full codebase | Stack traces + error context |
| Goal | Prevent bugs from shipping | Fix bugs that already shipped |
Sentry Autofix and Fix It For Me are complementary. Sentry fixes bugs after they hit production — and it's impressive: it generates unit tests from error context and continues iterating after the PR is opened. Fix It For Me fixes bugs before they're merged — during the GitHub PR review cycle. Different stages of the same goal: fewer bugs in production.
Fix It For Me vs. GitHub Copilot Autofix
| Fix It For Me | Copilot Autofix | |
|---|---|---|
| Scope | Full PR-level bug detection + fix | Inline code completion + suggestion |
| CI loop | Iterates until tests pass | No CI integration |
| Branch management | Creates branches, opens PRs | Inline suggestion only |
| Codebase awareness | Full AST graph of entire repo | Current file context |
Copilot suggests fixes inline while you code. Fix It For Me operates at the PR review stage — after the code is pushed — with full codebase context and CI validation. Different stages, different capabilities.
Fix It For Me vs. CodeRabbit Autofix
CodeRabbit offers two fix paths: 1-click commits for straightforward issues, and an AI-generated "Fix with AI" suggestion for more complex problems. Both operate within the review comment context. Fix It For Me takes a different approach: it creates a separate fix branch, opens a full PR, runs your CI pipeline, and iterates on failures until tests pass. For teams evaluating CodeRabbit alternatives, the key difference is whether fixes are applied inline (CodeRabbit) or go through a full branch-and-validate workflow (Fix It For Me).
Fix It For Me vs. Gitar
Gitar focuses on fixing CI failures — it reads failure logs, generates fixes, and commits working code. Fix It For Me fixes bugs found during code review, before CI even runs on the fix. Gitar reacts to red CI. Fix It For Me prevents the red CI from happening in the first place.
What Kinds of Bugs Does Fix It For Me Fix?
Fix It For Me can fix any bug that Macroscope's Correctness check detects. Macroscope categorizes findings by severity — CRITICAL (data loss, security breaches), HIGH (production crashes), MEDIUM (broken functionality), and LOW (cosmetic, edge cases). Examples of bugs Fix It For Me commonly resolves include:
- Runtime logic errors — off-by-one mistakes, incorrect conditional logic, wrong variable references
- Cross-file bugs — issues that appear only when changes in one file interact with code in another
- Null/nil handling — missing null checks, unsafe optional access
- Type mismatches — incorrect type conversions or interface violations
- Edge case failures — boundary conditions that the original code doesn't handle
Macroscope uses a dual detection approach: native AST-based analysis for supported languages (Go, Python, TypeScript, JavaScript, Vue.js (including Nuxt), Java, Rust, Kotlin, Swift, Ruby, Elixir, and Starlark) and an AI-powered agentic approach for other file types that includes web search for current library docs and deprecation notices. This deep, language-aware analysis is why Macroscope catches cross-file bugs that single-file reviewers miss, and why the fixes it generates account for the full codebase context.
How Does Fix It For Me Handle Branch Protection?
Macroscope never pushes directly to your main branch. All fix branches follow the macroscope/*/** naming convention. If you use branch protection rules, you may need to add this pattern to your allowed branches.
For GitHub Actions optimization, you can add branch-specific rules for macroscope/*/** to limit which actions run on fix branches — avoiding unnecessary deployment or notification workflows.
How Does Fix It For Me Handle Auto-Generated Code?
Repositories with auto-generated code (protobuf, GraphQL schemas, OpenAPI specs) need special handling. If your test suite produces expected diffs for generated files, Macroscope detects and applies these automatically as part of the fix workflow.
For example, if fixing a .proto file requires regenerating .pb.go files, and your test outputs include the expected generated diffs, Fix It For Me picks these up and includes them in the fix commit.
How Does Fix It For Me Fit into the GitHub Code Review Workflow?
Fix It For Me integrates into the standard GitHub pull request review flow:
- Developer opens a PR on GitHub
- Macroscope's AI code review runs automatically — the Correctness check detects bugs and posts review comments
- Developer replies "fix it for me" to a review comment
- Fix It For Me creates a fix branch, opens a PR, runs CI, iterates
- Fix is auto-merged or left for review based on settings
This means your GitHub code review process gains an automated remediation loop. The AI code reviewer finds the bug, and the AI code fixer resolves it — all within the GitHub PR workflow your team already uses.
For teams searching for the best AI code review tool or evaluating CodeRabbit alternatives and Greptile alternatives, Fix It For Me is a unique capability. No other GitHub code reviewer offers an integrated detect-and-fix workflow with CI validation.
What Does Fix It For Me Cost?
Fix It For Me is included with Macroscope's usage-based pricing at no additional cost. There is no separate fee for fix generation, branch creation, or CI iteration. The fix work is billed under the standard code review usage meter ($0.05 per KB reviewed).
Every new workspace gets $100 in free usage to start — enough for roughly 100+ code reviews and fixes.
How to Get Started with Fix It For Me
- Sign up for Macroscope at macroscope.com and install the GitHub App
- Push a PR — Macroscope automatically reviews it
- When Macroscope finds a bug, reply to the review comment asking for a fix
- Fix It For Me creates a branch, fixes the code, opens a PR, and runs CI
- Review and merge the fix, or let auto-merge handle it
Fix It For Me works on every repository where Macroscope is installed. No additional configuration required.
Want a custom setup? Book a demo to see Fix It For Me in action on your codebase.
Frequently Asked Questions
What is Fix It For Me?
Fix It For Me is Macroscope's AI code fixer. When Macroscope's AI code review detects a bug in your GitHub pull request, Fix It For Me automatically creates a new branch, implements the fix, opens a pull request, runs your CI checks, and iterates on failures until the fix passes. It turns review comments into working code.
How do I trigger Fix It For Me?
Reply to any Macroscope review comment on your GitHub pull request asking it to fix the issue. You can also trigger fixes via the @Macroscope Slack bot by asking it to fix a bug or implement a change.
Does Fix It For Me run my CI tests?
Yes. After implementing a fix, Fix It For Me triggers your existing GitHub Actions. If CI fails, Macroscope reads the failure logs, diagnoses the problem, and commits another fix attempt. This loop continues until your tests pass.
Can Fix It For Me auto-merge the fix?
Yes. You can say "fix it for me and auto-merge" to force merge on successful checks, or "fix it but don't auto-merge" to leave the PR for manual review. Auto-merge behavior is also configurable at the workspace level.
What kinds of bugs can Fix It For Me fix?
Fix It For Me can fix any bug detected by Macroscope's Correctness check, categorized by severity: CRITICAL (data loss, security), HIGH (crashes), MEDIUM (broken functionality), LOW (cosmetic/edge cases). Common fix types include runtime logic errors, cross-file bugs, null handling issues, type mismatches, and edge case failures. Macroscope uses native AST analysis for 12 languages plus an AI agentic approach for other file types.
Does Fix It For Me work on fork pull requests?
No. Fix It For Me is not available on cross-repo or fork pull requests. Macroscope still reviews these PRs when cross-repo review is enabled, but cannot create fix branches on external forks.
How much does Fix It For Me cost?
Fix It For Me is included with Macroscope's usage-based pricing at no additional fee. Fix work is billed under the standard code review meter ($0.05/KB reviewed). Every new workspace gets $100 in free usage.
Is Fix It For Me a good CodeRabbit alternative?
For teams evaluating CodeRabbit alternatives, Fix It For Me is a key differentiator. CodeRabbit offers 1-click commits for simple fixes and AI-generated suggestions for complex ones, both applied within the review context. Fix It For Me creates a separate fix branch, opens a full PR, validates against your CI pipeline, and iterates until tests pass — a full remediation workflow rather than inline fixes. See the full Macroscope vs CodeRabbit comparison.
How does Fix It For Me compare to Sentry Autofix?
Sentry Autofix fixes bugs after they hit production, using stack traces and error context. Fix It For Me fixes bugs before they're merged, during the GitHub PR review cycle. They're complementary: Fix It For Me prevents bugs from shipping, Sentry Autofix catches the ones that slip through.
How does Fix It For Me compare to DeepSource Autofix?
DeepSource Autofix generates one-shot fixes for static analysis findings. Fix It For Me generates fixes for deeper runtime bugs found during AI code review, opens a full PR, and iterates against your CI pipeline until tests pass. Fix It For Me also supports auto-merge.
How does Fix It For Me compare to GitHub Copilot Autofix?
Copilot suggests inline fixes while you code (in the editor). Fix It For Me operates at the PR review stage — after code is pushed — with full codebase context and CI validation. Copilot is a coding assistant. Fix It For Me is an automated remediation system.
How does Fix It For Me handle branch protection?
Fix It For Me never pushes directly to your main branch. All fix branches use the macroscope/*/** naming pattern. You may need to add this pattern to your branch protection allowed list. Fix It For Me respects all branch protection rules and required checks.
Can Fix It For Me handle auto-generated code?
Yes. If your test suite produces expected diffs for generated files (protobuf, GraphQL, OpenAPI), Fix It For Me detects and applies these automatically as part of the fix commit.