# Brimyr > Quality assurance for a pull request — auto-detect the ecosystem, run tests with coverage, and gate on the coverage of the lines a PR changed (diff-cover style) plus the net-new quality findings it introduced. Canonical documentation for Brimyr, served at https://docs.magmamoose.com/brimyr/. The full text of every page below is at `llms-full.txt`. Each link is the page's markdown. The page itself is the same address without the `index.md`, or with `.html` in place of `.md`. ## Docs - [Action reference](https://docs.magmamoose.com/brimyr/action/index.md): Every input and output of the magmamoose/brimyr composite action, with the default the code actually uses. Inputs are all optional. For the CLI behind it, see CLI reference. - [Architecture](https://docs.magmamoose.com/brimyr/architecture/index.md): Brimyr is one brimyr Python CLI (src/brimyr/cli.py:main) behind three GitHub surfaces, running two gates: patch coverage and net-new quality findings. The design splits cleanly into a pure core and a thin set of side-effecting edges. - [CLI reference](https://docs.magmamoose.com/brimyr/cli/index.md): All three GitHub surfaces drive the same brimyr CLI. Exit codes: 0 pass · 1 patch coverage below threshold, or blocking net-new quality findings · 2 broken test run / setup / usage error, a quality input the gate could not evaluate, or a quality scan that did not complete. A run that does both halves exits with the… - [.NET solutions](https://docs.magmamoose.com/brimyr/dotnet/index.md): Brimyr detects a .NET repo from .sln, .slnx, .csproj, .fsproj or *.vbproj, runs - [Go](https://docs.magmamoose.com/brimyr/go/index.md): Brimyr detects a Go module from go.mod plus at least one _test.go file that go test ./... would actually run, and runs - [HTML coverage report](https://docs.magmamoose.com/brimyr/html-report/index.md): Brimyr can render the coverage it produced as a browsable HTML report and upload it as a build artifact, so a repo with no SonarQube still has something to look at. - [Brimyr](https://docs.magmamoose.com/brimyr/index.md): Brimyr is quality assurance for a pull request: it gates on the coverage of the lines that PR changed, and on the net-new quality findings that PR introduced. Point it at any repo and it figures out the rest, it detects the ecosystem, runs the test suite with coverage instrumentation on, and gates on the coverage of… - [Java / JVM](https://docs.magmamoose.com/brimyr/java/index.md): Brimyr detects a Maven repo from pom.xml, runs - [Patch coverage](https://docs.magmamoose.com/brimyr/patch-coverage/index.md): Patch coverage is the fraction of changed executable lines the test run covered. A line counts iff it is changed by the PR: in an added/modified hunk on the new side, diffed against merge-base(base, head), and the coverage tool considers it executable. The merge-base survives base-branch rebases and force-pushes. - [PR comment](https://docs.magmamoose.com/brimyr/pr-comment/index.md): Brimyr can post its verdict as a comment on the pull request, so a reviewer sees the numbers without opening the job log. It is opt-in (pr_comment: 'true'), there is exactly one comment per marker: and the action's path uses one, and it is never able to change the gate verdict. - [Quality findings](https://docs.magmamoose.com/brimyr/quality-findings/index.md): Coverage is half of quality assurance. The other half is the findings a linter reports on the lines this PR changed: and Brimyr gates on those the same way it gates on coverage: net-new only, pre-existing never blocks. - [Setup & usage](https://docs.magmamoose.com/brimyr/setup/index.md): Brimyr gates a pull request on two things: patch coverage (always) and net-new quality findings (opt-in). It runs your tests on the runner, and by default it installs their dependencies first using whatever your repo already declares: uv run, poetry run, npm ci. So the minimal wiring is the action on its own, with no… - [Shell / bats](https://docs.magmamoose.com/brimyr/shell/index.md): Brimyr detects a shell repo from a real .bats file, runs - [SonarQube](https://docs.magmamoose.com/brimyr/sonarqube/index.md): Brimyr can ship coverage to SonarQube in the same run that gates the pull request. Set two inputs and the action installs a scanner for you: - [Troubleshooting](https://docs.magmamoose.com/brimyr/troubleshooting/index.md): Symptom, cause, fix. Exit codes first, because they tell you which half of the page you're in.