Skip to main content

​
Using Code Review

Macroscope automatically reviews every pull request for quality and correctness. When Macroscope spots a bug, it will:
  1. Add a GitHub comment — describing the issue in clear language, referencing the exact code, and explaining the potential impact.
  2. Suggest a fix — proposing a diff that can be applied to fix the bug.
Engineers can give feedback to Macroscope’s suggestions with 👍 or 👎 reactions — this feedback helps Macroscope improve code review.
Feedback appears as a standard review comment in GitHub, alongside comments from human reviewers. You can engage and converse with Macroscope directly on GitHub. Bug Finding and Fixing

​
Configuring Code Review

By default, Code Review is automatically enabled on every repository you link to Macroscope.
  • You can change the default setting that gets applied to newly linked (in the future) repositories in Settings -> Repos -> “Defaults”.
  • You can enable/disable Code Review on a per-repository basis in Settings.
  • You can manually trigger a code review on a Pull Request (even if Code Review is turned off in that repository) by leaving an issue comment that includes “@macroscope-app review”. This is helpful for evaluating code review on repos where code review is not on by default