> For the complete documentation index, see [llms.txt](https://docs.sonarsource.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sonarsource.com/agent-centric-development-cycle/in-your-pull-requests-the-ci-verification-loop/ci-verification-loop.md).

# What is the CI verification loop?

Once a human or an agent has pushed code to the repository and opened a pull request, the pipeline and all verifications run to detect problems, trigger quality gates, and prevent merging low-quality code into the main branch.

Verification is zero-trust and multi-layered, which means no single check is trusted on its own. Two layers work together on your pull request:

* SonarQube analysis runs on the new code, raises issues as inline comments on the pull request, and computes the [quality gate](/sonarqube-cloud/standards/managing-quality-gates/introduction-to-quality-gates.md) that decides whether the code is fit to merge. See [Pull request analysis](/sonarqube-cloud/analyzing-source-code/pull-request-analysis.md).
* [Gitar](https://docs.gitar.ai/introduction) adds AI-powered code review to your pull requests: inline comments, summaries, walkthroughs, and diagrams.


---

# 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://docs.sonarsource.com/agent-centric-development-cycle/in-your-pull-requests-the-ci-verification-loop/ci-verification-loop.md?ask=<question>&goal=<endgoal>
```

`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.