Update to SonarQube

{
  "name": "sonar-list-projects",
  "description": "List SonarQube projects accessible to the current user",
  "included_files": [],
  "skill_md_contents": "---\nname: sonar-list-projects\ndescription: List SonarQube projects accessible to the current user\nargument-hint: \"[search-query]\"\nallowed-tools: Bash(sonar:*)\n---\n\n# SonarQube — List Projects\n\nList SonarQube projects accessible to the authenticated user. Useful for discovering project keys before running other skills.\n\n## Usage\n\n```\nsonar-list-projects                      # list all accessible projects\nsonar-list-projects my-project              # search by name or key\n```\n\n## Prerequisites\n\nThis skill uses the `sonarqube-cli` command. The CLI must be installed and authenticated before proceeding.\n\n**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:\n\n> Unable to list projects.\n>\n> **Possible causes:**\n> - `sonarqube-cli` not installed or not authenticated — invoke the sonar-integrate skill\n\nThen 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.\n\n## Instructions\n\n### Step 1: Parse optional search term from the user-provided arguments\n\n- If the user provided a search term (not a flag), pass it as `--query`.\n\n### Step 2: Validate arguments\n\nIf 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.\n\n### Step 3: Run `sonar list projects`\n\nBuild and run the command using a shell command:\n\n```bash\nsonar list projects [--query <search-term>]\n```\n\nOnly include `--query` if a search term was provided.\n\n### Step 4: Format the results\n\n**If projects are found**:\n\n```markdown\n## SonarQube Projects\n\nFound **8 project(s)**:\n\n| Project key       | Name            |\n| ----------------- | --------------- |\n| my-org_backend    | Backend Service |\n| my-org_frontend   | Frontend App    |\n| my-org_shared-lib | Shared Library  |\n```\n\n**If no projects are found**:\n\n```markdown\n## SonarQube Projects\n\nNo projects found. If you expected results, check your authentication with `sonar auth status`.\n```\n\n**If the result is paginated** (500 projects returned), note: *\"Showing first 500 projects. Use a search term to narrow results.\"*\n\n### Step 5: Next steps\n\n- 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`.\"*\n- 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.\"*\n"
}