> 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-cloud/discovering-sonarcloud/developing-with-sonar.md). # Developing with Sonar The Sonar solution helps developers find address issues effectively, so code is only promoted when the code is secure and passes the quality gate. The SonarQube solution helps developers perform automated code analysis and reviews at every stage of the development process: * SonarQube for IDE provides immediate feedback in your IDE as you write code so you can find, focus on, and fix anticipated issues before a commit. * SonarQube Cloud’s PR analysis fits into your cloud-based CI/CD workflows so that you merge high-quality code every time. * Quality gates keep code with issues from being released to production. See [Quality standards and new code](/sonarqube-cloud/standards/about-new-code.md) for more details. Organizations start with a set of default rules called the Sonar way core quality profile. Quality profiles define the set of [SonarQube rules](/sonarqube-cloud/standards/managing-rules/rules.md) to be applied during code review and analysis. You can extend Sonar way core in a custom quality profile to satisfy different technical requirements. See [Understanding quality profiles](/sonarqube-cloud/standards/managing-quality-profiles/understanding-quality-profiles.md) for more information. A quality gate is an indicator of code quality that can be configured to give a green or red light on the current release-worthiness of your code. It indicates whether your code complies with the quality standards and can move forward. See [Understanding quality gates](/sonarqube-cloud/standards/managing-quality-gates/introduction-to-quality-gates.md) for more information. * A **Passed** (green) quality gate means the code meets your standard and is ready to be merged. * A **Failed** (red) quality gate means there are issues to address. SonarQube Cloud provides feedback through its UI, email, and in decorations on pull or merge requests to notify your team that there are issues to address. SonarQube Cloud also provides in-depth guidance on the issues telling you why each issue is a problem and how to fix it, adding a valuable layer of education for developers of all experience levels. Feedback can also be obtained during automated code review in [SonarQube for IDE](/sonarqube-cloud/analyzing-source-code/connected-mode.md) when running in Connected Mode. SonarQube for IDE helps developers find, focus on, and fix anticipated issues before a commit. Together, SonarQube for IDE and SonarQube Cloud help developers address issues effectively, so only high-quality code that passes the quality gate is promoted. Explore featured public projects on SonarQube Cloud and experience how other organizations leverage the platform to improve their code. See [Retrieving your organizations](/sonarqube-cloud/getting-started/viewing-organizations.md#free-organization). --- # 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://docs.sonarsource.com/sonarqube-cloud/discovering-sonarcloud/developing-with-sonar.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.