How it works

The Mergestorm feedback loop on every pull request

Start with one GitHub App: Vortex reviews every PR with inline comments and check runs. Cyclone auto-patch is an optional add-on when you want fixes committed for you. Connect Vortex, open a PR, and get value immediately. 30 free credits every month.

Getting started

Five steps from zero to your first automated PR review.

  1. 1

    Set up a GitHub repository

    You need a GitHub repository with your project code. An existing repo works perfectly — there is nothing new to create.

  2. 2

    Sign in to Mergestorm

    Create your Mergestorm account in seconds with Google or GitHub. No credit card required to start.

  3. 3

    Deploy Vortex

    On Agents, install the Vortex GitHub App on the repos you want reviewed — one install is enough for automatic reviews.

  4. 4

    Enable automatic reviews

    In Settings, turn on automatic PR reviews so Vortex runs on every push. Auto-patch stays off until you opt in later.

  5. 5

    Open a pull request

    Open a PR and let Vortex comment on the diff — or use the PR activity list on Work to trigger a review of any open PR (and stop one mid-flight) and watch its status flow live. Add Cyclone later if you want auto-patch.

The recommended workflow

The core path is simple: connect Vortex, enable auto-review, open a pull request, and watch reviews land on GitHub. Optionally add Cyclone later for auto-patch — then each push can review and fix in a loop.

  • Vortex reviews

    On every open PR and push, Vortex posts inline comments and a check run — a fast first pass on what changed.

  • Cyclone fixes

    When auto-patch is on, Cyclone takes actionable findings from those reviews and commits fixes straight to the PR branch.

  • The loop continues

    New commits trigger another review pass and another round of fixes. That back-and-forth is the Mergestorm feedback loop.

  • Then your second pass

    When the storm has done its work, hand off to your team or whatever deeper review process you already trust for the final look.

Dashboard chat

You can use Dashboard Chat to quote a PR, layer, or stack from the Work tab, paste a PR link (quoted as a chip automatically), or ask questions about your setup, Vortex, or Cyclone. Chat takes no file uploads and does not write code — it acts on connected Work objects only.

Chat is great for exploration and quick questions. For day-to-day work on real repos, the GitHub loop above is what we recommend: let the agents run on the PR while you review the commits they leave behind.

On every pull request

Once Vortex is connected and auto-review is on, you do not need to babysit each change. Every PR open and push triggers Vortex; if you later enable auto-patch with Cyclone, fixes can follow on the same branch.

Want a review on demand? Comment @mergestorm-vortex review on the pull request and Vortex will run a fresh pass.

What each agent does

Vortex is required for reviews. Cyclone is optional when you want auto-patch.

Vortex

  • Prepares your code

    Vortex pulls a fresh view of your repository so it can reason about your code the way a teammate would.

  • Focuses on the diff

    Instead of re-reading everything, it zeroes in on what your pull request actually changed.

  • Reads the linked issue

    If the PR closes or links a GitHub Issue, Vortex uses that ticket as context so reviews match the intended fix — not just the patch.

  • Posts feedback

    Inline comments and a GitHub check land on the PR — a quick first pass so humans can focus on what matters.

Cyclone

  • Reads review output

    Cyclone watches for actionable fixes in Vortex review comments — not random edits, just what the review surfaced.

  • Commits to the branch

    When auto-patch is enabled, Cyclone pushes those fixes onto the PR branch so you can review them like any other commit.

  • Optional add-on

    Cyclone is a separate GitHub App you add only when you want auto-patch — reviews work with Vortex alone.

Vortex is built for a fast first pass on what changed. Cyclone handles the mechanical fixes from that pass — not a replacement for your team's judgment, security review, or whatever deeper second look you already run after automation.

Ready to start the loop?

Connect Vortex, turn on auto-review, and open your next pull request on GitHub. Add Cyclone later if you want auto-patch.