> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/codescan/quality-gates/understanding-quality-gates.md).
# Understanding Quality Gates
## **What Is a Quality Gate?**
A quality gate is an indicator that determines whether your code meets the minimum quality standards for your project. It consists of a set of conditions applied to the results of each analysis. If the results meet or exceed these conditions, the status is "Passed"; otherwise, it is marked as "Failed."
A Quality Gate consists of measure-based, Boolean conditions that allow you to quickly assess whether your projects are production-ready. Ideally, all projects should utilize the same quality gate, with each project's quality gate status clearly visible on its homepage.
CodeScan will provide standard values for each metric in the default (built-in) quality gate (sonar way). However, the quality gate can be customized to align with your organization’s standards.
**Important Note:** Built-in quality gates are standard and cannot be edited.
See more information on [Sonar Way](https://docs.sonarsource.com/sonarqube-cloud/standards/managing-quality-gates/introduction-to-quality-gates/), the recommended quality gate. We consider these conditions for our default quality gate.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://knowledgebase.autorabit.com/product-guides/codescan/quality-gates/understanding-quality-gates.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
