Code Quality Overview

For the complete documentation index, see llms.txt. This page is also available as Markdown.

AI-powered code quality checks on pull requests and full-repository scans.

Quality checks on new code — scan changed lines on every pull request.

Quality checks on existing code — full-repo scores, findings, and hotspots.

Define team-specific checks beyond the defaults.

Give Aikido background on your codebase and conventions.

Suppress findings on lines you've reviewed and accepted.

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.

Code Quality splits cleanly across two modes:

New code — lines added or changed in a pull request

Existing code — the full codebase as it stands today

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.

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.

Repository scans are in early access and rolling out soon. If you don't see the Repositories tab under Code Quality yet, open the Intercom chat in the bottom right corner — our team can enable early access for your workspace.

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

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

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

Don't see your language listed? Reach out in intercom. We can look at adding it.

Supported languages

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