Update to SonarQube

SKILL.md text changes

− removed · + added

--- before
+++ after
@@ -1,81 +1,81 @@
----
-name: sonar-list-projects
-description: List SonarQube projects accessible to the current user
-argument-hint: "[search-query]"
-allowed-tools: Bash(sonar:*)
----
-
-# SonarQube — List Projects
-
-List SonarQube projects accessible to the authenticated user. Useful for discovering project keys before running other skills.
-
-## Usage
-
-```
-sonar-list-projects                      # list all accessible projects
-sonar-list-projects my-project              # search by name or key
-```
-
-## Prerequisites
-
-This skill uses the `sonarqube-cli` command. The CLI must be installed and authenticated before proceeding.
-
-**Before proceeding**, verify that `sonar` is available on your PATH and authenticated. If it is not, do not attempt to call any alternative commands or invent alternatives, and show the user:
-
-> Unable to list projects.
->
-> **Possible causes:**
-> - `sonarqube-cli` not installed or not authenticated — invoke the sonar-integrate skill
-
-Then ask the user (yes/no) whether to run the sonar-integrate skill now. Briefly explain what it does: it checks the SonarQube setup on their machine — installing or updating `sonarqube-cli` and verifying authentication — and re-configures the integration for this agent, including the SonarQube MCP server and secrets-scanning hooks. If they confirm, invoke the sonar-integrate skill yourself and follow it end-to-end in this session, then re-check and continue; if they decline, stop.
-
-## Instructions
-
-### Step 1: Parse optional search term from the user-provided arguments
-
-- If the user provided a search term (not a flag), pass it as `--query`.
-
-### Step 2: Validate arguments
-
-If a `--query` search term was provided, validate it matches `^[a-zA-Z0-9_\-\. ]+$`. If it does not, stop and tell the user what was rejected — do not run the command.
-
-### Step 3: Run `sonar list projects`
-
-Build and run the command using a shell command:
-
-```bash
-sonar list projects [--query <search-term>]
-```
-
-Only include `--query` if a search term was provided.
-
-### Step 4: Format the results
-
-**If projects are found**:
-
-```markdown
-## SonarQube Projects
-
-Found **8 project(s)**:
-
-| Project key       | Name            |
-| ----------------- | --------------- |
-| my-org_backend    | Backend Service |
-| my-org_frontend   | Frontend App    |
-| my-org_shared-lib | Shared Library  |
-```
-
-**If no projects are found**:
-
-```markdown
-## SonarQube Projects
-
-No projects found. If you expected results, check your authentication with `sonar auth status`.
-```
-
-**If the result is paginated** (500 projects returned), note: *"Showing first 500 projects. Use a search term to narrow results."*
-
-### Step 5: Next steps
-
-- To list issues: *"Invoke the sonar-list-issues skill with the project key, or ensure `sonar.projectKey` is in `sonar-project.properties` — the CLI always requires `-p`."*
-- To check the quality gate: *"Invoke the sonar-quality-gate skill — add a project key only if you are not using the MCP integration default."*
+---
+name: sonar-list-projects
+description: List SonarQube projects accessible to the current user
+argument-hint: "[search-query]"
+allowed-tools: Bash(sonar:*)
+---
+
+# SonarQube — List Projects
+
+List SonarQube projects accessible to the authenticated user. Useful for discovering project keys before running other skills.
+
+## Usage
+
+```
+sonar-list-projects                      # list all accessible projects
+sonar-list-projects my-project              # search by name or key
+```
+
+## Prerequisites
+
+This skill uses the `sonarqube-cli` command. The CLI must be installed and authenticated before proceeding.
+
+**Before proceeding**, verify that `sonar` is available on your PATH and authenticated. If it is not, do not attempt to call any alternative commands or invent alternatives, and show the user:
+
+> Unable to list projects.
+>
+> **Possible causes:**
+> - `sonarqube-cli` not installed or not authenticated — invoke the sonar-integrate skill
+
+Then ask the user (yes/no) whether to run the sonar-integrate skill now. Briefly explain what it does: it checks the SonarQube setup on their machine — installing or updating `sonarqube-cli` and verifying authentication — and re-configures the integration for this agent, including the SonarQube MCP server and secrets-scanning hooks. If they confirm, invoke the sonar-integrate skill yourself and follow it end-to-end in this session, then re-check and continue; if they decline, stop.
+
+## Instructions
+
+### Step 1: Parse optional search term from the user-provided arguments
+
+- If the user provided a search term (not a flag), pass it as `--query`.
+
+### Step 2: Validate arguments
+
+If a `--query` search term was provided, validate it matches `^[a-zA-Z0-9_\-\. ]+$`. If it does not, stop and tell the user what was rejected — do not run the command.
+
+### Step 3: Run `sonar list projects`
+
+Build and run the command using a shell command:
+
+```bash
+sonar list projects [--query <search-term>]
+```
+
+Only include `--query` if a search term was provided.
+
+### Step 4: Format the results
+
+**If projects are found**:
+
+```markdown
+## SonarQube Projects
+
+Found **8 project(s)**:
+
+| Project key       | Name            |
+| ----------------- | --------------- |
+| my-org_backend    | Backend Service |
+| my-org_frontend   | Frontend App    |
+| my-org_shared-lib | Shared Library  |
+```
+
+**If no projects are found**:
+
+```markdown
+## SonarQube Projects
+
+No projects found. If you expected results, check your authentication with `sonar auth status`.
+```
+
+**If the result is paginated** (500 projects returned), note: *"Showing first 500 projects. Use a search term to narrow results."*
+
+### Step 5: Next steps
+
+- To list issues: *"Invoke the sonar-list-issues skill with the project key, or ensure `sonar.projectKey` is in `sonar-project.properties` — the CLI always requires `-p`."*
+- To check the quality gate: *"Invoke the sonar-quality-gate skill — add a project key only if you are not using the MCP integration default."*