analyzeUse when the user asks to "run sonar", "run SonarQube", "run SonarLint", "scan for secrets", "check this for Sonar issues", or wants SonarQube analysis over code this session never touched. Runs SonarQube for IDE's engine locally, adds what SonarQube Server or Cloud recorded for the same files, and
fixUse when the user asks to fix SonarQube or SonarLint issues, a specific Sonar rule key (like python:S5754 or githubactions:S8541), or "the Sonar findings" in some files, including issues SonarQube Server or Cloud reported. Gathers findings locally and from the server, explains each rule, and fixes t
setupUse when the user asks to install, set up, update, or repair the SonarQube plugin's local analysis engine, when `sonarlint` exits 2 or `doctor` reports a failure, or when a hook says local analysis could not run or SLOOP is not installed.
sonarlint-analysisUse after creating or editing source code (JS/TS, Python, Java, Go, PHP, HTML, CSS, XML, Terraform, Docker, Kubernetes, CloudFormation, or any file that could hold a credential) and before declaring a coding task done, or when asked to check code quality or security locally. Runs SonarQube for IDE's
sonarqube-connected-modeUse when you need a SonarQube projectKey, are setting up or debugging .sonarlint/connectedMode.json, are calling `sonar api` against a bound project, need the Cloud organization, or are working out which project a file in a monorepo belongs to.
sonarqube-issue-triageUse when acting on SonarQube findings — deciding what to fix first, whether something is a real defect or a false positive, how to handle a detected secret, what a quality gate failure means, or whether a NOSONAR suppression is ever justified.
sonarqube-web-apiUse when you need data from a SonarQube Server or SonarQube Cloud instance — open issues or security hotspots on a project, a quality gate verdict, a rule's rationale, measures or coverage, branches and pull requests, duplications, or changing an issue's status. Covers calling the Web API through `s