Mergestorm

How it works

The Mergestorm feedback loop on every pull request

Mergestorm runs autonomous Storm Agents on your repos. Vortex reviews every PR; Cyclone can auto-apply those fixes when you turn on auto-patch. Connect both, open a PR, and let the storm run — that is the best way to use the product right now. 100 free reviews every month.

Getting started

Five steps from zero to your first automated review-and-fix loop.

  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 and Cyclone

    On Automation, connect both Storm Agents on the repos you want in the loop — Vortex for reviews, Cyclone for auto-fixes.

  4. 4

    Enable auto-review and auto-fix

    In Settings, turn on automatic PR reviews and auto-patch. Fixes stay off until you opt in — you control when Cyclone commits.

  5. 5

    Open a pull request

    Open a PR and let the loop run. Vortex comments on the diff; Cyclone can push fixes to the branch. Every push keeps the storm going.

The recommended workflow

The name is the playbook: connect Vortex and Cyclone, enable auto-review and auto-fix, open a pull request, and watch the feedback loop run on GitHub. Vortex comments; Cyclone pushes fixes; the next push starts another round.

  • 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 always use Dashboard Chat like a normal assistant — paste code, drop a PR link, or ask questions about your setup, Vortex, or Cyclone.

Chat is great for exploration and one-off audits. 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 both agents are connected and automation is on, you do not need to babysit each change. Every PR open and push triggers Vortex; with auto-patch enabled, Cyclone follows with fixes on the same branch.

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

What each agent does

Two focused agents, one loop — review first, fix second.

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.

  • 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.

  • Separate GitHub App

    Cyclone installs on its own from Vortex, so you connect reviews and auto-fix on your terms.

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 and Cyclone, turn on auto-review and auto-patch, and open your next pull request on GitHub.

Open chat