Skip to content
View source on GitHub

Code quality, orchestrated

One command.
Every tool.

Your tools already know good code.
Give them one shared workflow.

Run trusted analyzers across languages, repositories, and CI. Keep the checks explicit and the feedback useful.

Deterministic. Local. Yours.

A familiar place to start
consoleExample · mixed repository
$ quality check --changed origin/main

  ✓ SwiftLint
  ✓ SwiftFormat
  ✓ Android Lint
  ✓ detekt
  ✓ ESLint

Quality checks passed (5 tools).

Native tools.
One clear answer.

Built for the whole repositoryOpen source / MIT
One workflow across

RustSwiftAndroid & KotlinPythonJavaScript & TypeScriptAstro

01 The everyday loop

Less glue.
Better signal.

Keep the ecosystem tools you trust. Spend less time connecting them.

02 Start with your repository

Three commands.
A clearer routine.

Initialize a policy, check your toolchain, then run it. Existing repository gates stay part of the workflow.

Install quality
bash
quality init
quality doctor
quality check

Run from the repository you want to check.
Explore the command reference

03 Under the hood

Native tools in.
One answer out.

A thin orchestration layer, with each analyzer’s behavior as the source of truth. No AI service in the checking path.

  1. 01

    Detect

    Read repository intent and the ecosystems already in use.

  2. 02

    Resolve

    Prefer the repository’s own tools and configuration.

  3. 03

    Run

    Execute independent analyzers concurrently.

  4. 04

    Report

    Bring findings and failures into one predictable result.

04 Keep going

Make it your workflow.

Read the docs