English

Code Quality Overview

AI-powered code quality checks on pull requests, full-repository scans, and test coverage from CI.

Set Up PR Checks
Quality checks on new code: scan changed lines on every pull request.
Repository Scans
Quality checks on existing code: full-repo scores, findings, and hotspots.
Code Coverage
Upload coverage reports from CI, track coverage per repository and file, and fail pull requests below a threshold.
Add Custom Code Rules
Define team-specific checks beyond the defaults.
Add Extra Code Context
Give Aikido background on your codebase and conventions.
Ignore Specific Lines
Suppress findings on lines you've reviewed and accepted.

What is Code Quality?

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

It is the quality counterpart to SAST: checks on new code as you add it, once you enable them. It does not replace Deep Review. Deep Review covers both security and quality, with context beyond the changed lines.

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 across these modes:

ModeWhat it covers
PR checksNew code: lines added or changed in a pull request
Repository scansExisting code: the full codebase as it stands today
Code CoverageTest coverage: reports uploaded from CI, with optional PR gating on a minimum percentage

Use either quality 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. Add Code Coverage to see how much of that code your tests actually exercise, and fail pull requests that fall short of a coverage threshold.

PR checks for 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 for 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
  • Track test coverage: Upload coverage from CI, see it per repository, file, and line, and fail pull requests below a threshold

Supported languages

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
  • ABAP (SAP)
  • angular
  • Ansible
  • Apex (Salesforce)
  • C/C++
  • C#
  • Clojure
  • COBOL
  • ColdFusion
  • Dart
  • Delphi
  • Docker
  • Elixir
  • Erlang
  • go
  • Groovy
  • Haskell
  • Java
  • JS
  • JSON
  • Julia
  • Kotlin
  • Kubernetes / Helm charts
  • Lua
  • MySQL
  • OCaml
  • OpenEdge
  • Pascal
  • perl
  • PHP
  • PL/SQL
  • PowerShell
  • PY
  • R
  • react
  • Ruby
  • Rust
  • Scala
  • shell
  • Solidity
  • SQL
  • svelte
  • Swift/Objective-C
  • Terraform
  • TS
  • Visual Basic
  • vue
  • YAML
  • Zig

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