> 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/sonarqube-cli/analysis.md).

# Analysis

- [Overview](https://docs.sonarsource.com/sonarqube-cli/analysis/analysis.md): Use SonarQube CLI to catch issues before they reach a pull request: scan for secrets, verify local changes against SonarQube Cloud, and apply AI-suggested fixes.
- [Analyzing local changes](https://docs.sonarsource.com/sonarqube-cli/analysis/analyzing-local-changes.md): Run every SonarQube CLI analysis on your uncommitted, staged, or branch-diff changes, and get server-grade results in your terminal in seconds.
- [AI remediation](https://docs.sonarsource.com/sonarqube-cli/analysis/ai-remediation.md): Use SonarQube CLI to send eligible SonarQube issues to the AI remediation agent and apply suggested fixes from your terminal.
- [Secrets detection](https://docs.sonarsource.com/sonarqube-cli/analysis/secrets-detection.md): Detect hardcoded credentials before they reach a repository, an AI tool, or production. The SonarQube CLI's secrets detection works on demand, in Git, and inside AI coding sessions.
- [Software Composition Analysis (SCA)](https://docs.sonarsource.com/sonarqube-cli/analysis/sca.md): Use SonarQube CLI to scan your project's open-source dependencies for known vulnerabilities, malware, and prohibited licenses using SonarQube's Software Composition Analysis (SCA) engine.


---

# 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/sonarqube-cli/analysis.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.