Atlarix Reviewer

    A reviewer on every pull request, that never runs your code

    The reviewer reads pull requests on the repositories you choose and posts its findings as a review. It never writes to your code.

    Unlimited repositories · unlimited pull requests

    Findings, not a score

    Each finding names the file and line, what is wrong, and the specific fix — as review comments on the pull request, not a score.

    atlarixagent commented on this pull request
    Critical · correctness isFresh compares a millisecond delta against a seconds constant
    src/cache/provider-cache.ts:88
    How it fails: Every cached entry is treated as stale after ~0.9 seconds, so the cache never hits.

    Every candidate finding is checked a second time before it is posted. The ones that do not survive that check are counted, not shown — a reviewer that cries wolf gets muted, and a muted reviewer reviews nothing.

    It never executes your code

    It reasons about your code and never executes, builds, or tests it. There is no runner to compromise and no build step to poison.

    What it asks GitHub for
    contents: read · pull requests: write
    What it never does
    push · merge · build · run tests

    A review that did not finish says so, in the review. It never reports a pull request as clean because it failed to read it. How we handle your code →

    Three steps

    01
    Install on GitHub
    Pick the repositories you want reviewed. Read access to their contents, write access to pull-request reviews — nothing else.
    02
    Connect your account
    GitHub sends you back to Atlarix to link the installation. One click, and only you can link an installation you administer.
    03
    Open a pull request
    The next pull request opened on those repositories gets reviewed automatically. Mention @atlarixagent to ask for another pass.

    Pricing

    Included with Atlarix Pro. Unlimited repositories, unlimited pull requests.

    Reviews run on Atlarix Core, so they need a funded balance — either the allowance that comes with Pro, or pay-as-you-go credit. Either way it is the same balance the app spends from, metered per review; your account page shows what reviewing has spent, separately from the app.

    Per developer, never per repository

    Charging per repository punishes the teams with the most pull requests and the most to gain from reviewing them, and it makes you choose which repositories deserve a reviewer. Install it everywhere, on as many repositories as you like.

    Put it on your next pull request

    Already installed? Connect it at /reviewer/setup