Every code change ends in GitHub, as a pull request.

Install the GitHub App on a repository and the PR Reviewer reads each pull request against your architecture and documentation after CI passes. When other software work changes code — an incident fix, a ticket, a scheduled chore — it returns as a pull request here too.

Try it on one real change

A 45-minute live call. We connect one repository, and you can remove access after.

See code review on GitHub

How GitHub connects

  1. 01

    Install the Echelar GitHub App on the repositories you choose.

  2. 02

    Let Echelar build the repository's sandbox environment from its own setup.

  3. 03

    Turn on the PR Reviewer — after reading its private rehearsal reviews on pull requests you already merged, if you choose to run them.

What Echelar does in GitHub

Review after CI
Findings by severity, posted as one GitHub review once required checks pass. Each finding cites the file and the documented convention it rests on.
Fix on your signal
When the Reviewer requests changes, a person can start a separate fix Session — from the Reviews page, or automatically by adding the echelar label to the pull request. It pushes a commit to the branch and review starts again.
Certify checks at the commit
A status confirms that required checks passed at that exact commit — evidence, not a promise about the code.

What it cannot do

Limits are part of the integration, not a setting. The security page covers where code runs and who can enable what.

  • Push to a branch from the Reviewer — its token is read-only on code.
  • Merge a pull request; there is no merge capability.
  • Act on repositories where the App is not installed.
Read the security overview

Bring the real one.

One repository, connected live, in 45 minutes with the founder.

Try it on one real change