> For the complete documentation index, see [llms.txt](https://help.aikido.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.aikido.dev/code-quality/repository-scans.md).
# Code Quality Repository Scans
{% hint style="info" %}
Repository scans are in **early access** and rolling out soon. If you don't see the **Repositories** tab under Code Quality yet, contact us via Chat.
{% endhint %}
Repository scans show the code quality issues that already exist across your entire repository. Use them to find and prioritize technical debt, then keep the results up to date as your code changes.
Unlike [Code Quality in PRs](/code-quality/code-quality-setup.md), which checks only new code before you merge it, repository scans analyze **existing code**. Use both to stop new quality debt from entering your repository while working through what is already there.
## What it does
After Aikido scans a repository, you can:
* See open findings grouped into **maintainability**, **readability**, **performance**, and **reliability**
* Prioritize the categories and files that need attention first
* Track how open findings change over time
* Use [AutoFix](/autofix-and-remediation/overview-aikido-autofix.md) or fix findings yourself
## Start a scan
To set up a repository scan, see [Start a Repository Scan](/code-quality/repository-scans/start-a-repository-scan.md). It explains the prerequisites, yearly credit cost, and how to start tracking a repository.
## Explore your results
The **Repositories** tab gives each scanned repository a rating and finding count for the four quality categories. Open a repository to review the underlying findings, affected files, severity, and estimated fix time.
### See how quality changes
Open the **Trend Over Time** tab to see how the repository's open findings change from week to week. The chart splits findings by severity, so you can tell whether critical, high, medium, or low-priority quality debt is growing or shrinking.
Use it to measure the impact of cleanup work and spot regressions that need attention.
### Find file hotspots
The **File Scatter Plot** helps you prioritize cleanup work. Files in the top-right are your hotspots: they change frequently and have many open code quality findings.
{% hint style="info" %}
The File Scatter Plot requires both repository scans and [Code Quality in PRs](/code-quality/code-quality-setup.md) for the same repository. Repository scans provide the finding count, while PR checks provide the activity data.
{% endhint %}
For details about ratings, findings, and the scatter plot, see [Understand Repository Scan Results](/code-quality/repository-scans/understand-repository-scan-results.md).
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://help.aikido.dev/code-quality/repository-scans.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.