How to Trigger
- From GitHub: reply to a Macroscope review comment asking it to fix the issue.
- From Slack: ask
@Macroscopeto fix a bug or make a change.
Fix-it-for-me is not available on cross-repo or fork pull requests. Macroscope will still review these PRs if cross-repo review is enabled, but will not offer fix-it-for-me suggestions.
How It Works
- Macroscope creates a new branch off the feature branch (if triggered from GitHub) or main (if from Slack).
- Macroscope writes the fix and commits it.
- Macroscope opens a PR.
- Your GitHub Actions run. If any fail, Macroscope attempts to fix them and pushes again.
- If auto-merge is enabled, Macroscope merges the PR once all checks pass. PRs against main always require manual merge.
Auto-Merge
You can override auto-merge per fix:- “Fix it for me and auto-merge”: merges once checks pass, even if auto-merge is off by default.
- “Fix it but don’t auto-merge”: opens the PR but leaves it for manual merge.
Branch Protection
Macroscope never writes directly to main. All branches follow the patternmacroscope/*/**. If you have branch protection rules that apply to all branches, you may need to exclude this pattern.
GitHub Actions
Macroscope uses your existing GitHub Actions to validate fixes. To reduce latency or cost, add branch-specific rules formacroscope/*/** to limit which actions run.
Generated Code
If your repo has auto-generated code, include the expected diff in your test output. Macroscope will detect and apply it automatically.Example Test
Example Test