Code Quality Overview

What is Code Quality?

Code Quality helps you maintain high standards across your codebase — on the new code you ship and the existing code already in your repos.

Aikido applies AI-powered checks against your team's enabled rules. Findings include plain-language explanations and fix guidance, so developers can act on them without being security experts.

How it works

Code Quality splits cleanly across two modes:

Use either mode on its own, or both together. PR checks stop quality from getting worse; repository scans show you what's already there and where to focus cleanup.

PR checks — new code

On every pull request, Aikido scans only the lines you changed and leaves inline comments (or fails the gate, if you configure it that way). This catches regressions before they merge and keeps new contributions aligned with your standards.

See Set Up PR Checks for the full setup flow.

Repository scans — existing code

A full-codebase scan scores each repository across four quality categories, lists every open finding in code that's already merged, and highlights hotspots where high churn meets low quality.

See Repository Scans for setup, pricing, and how to read results.

Use cases

• Guard new code at review time — PR checks on changed lines, with optional gate failures

• Understand existing code health — category scores across the full codebase per repository

• Prioritize legacy cleanup — scatter plot hotspots where frequently changed files carry the most debt

• Enforce team standards — custom rules and code context tailored to your conventions

• Cover both layers — PR checks on every merge; repository scans with incremental rescans during your yearly subscription

Supported languages

Code Quality supports a wide and growing set of languages and frameworks. Click below for the full list.

For ignoring findings via .aikido configuration files in your repository, see Ignore via Code with Aikido Files.