Update to SonarQube

Snapshot Oct 28, 2026 · 12:32 UTC · version 2.7.0

Collection source: downloaded plugin package. These snapshots do not have a confirmed matching collection source. Differences in file lists alone do not establish changes to the package.

WHAT CHANGED

Instructions updated for sonar-fix-issue

Skill instructions — Now says: --- name: sonar-fix-issue description: Fix a specific SonarQube issue in code by rule key and location argument-hint: "[rule-key]...

Observed in instructions or declared skills. Runtime behavior has not been tested.

Save SonarQube and check future changes in Following.

Up to 3 plugins free · no card required.

All fields and original values.

Skill instructions

Before

Sep 30, 2026 · 23:13 UTC

--- name: sonar-fix-issue description: Fix a specific SonarQube issue in code by rule key and location argument-hint: "[rule-key] [file-path:line]" allowed-tools: Read, Edit, Bash(sonar:*) --- # SonarQube — Fix Issue Fix a code quality...

After

Oct 28, 2026 · 12:32 UTC

Compare saved observations

Download comparison JSON

SKILL.md text changes

− removed · + added

--- before
+++ after
@@ -1,59 +1,59 @@
----
-name: sonar-fix-issue
-description: Fix a specific SonarQube issue in code by rule key and location
-argument-hint: "[rule-key] [file-path:line]"
-allowed-tools: Read, Edit, Bash(sonar:*)
----
-
-# SonarQube — Fix Issue
-
-Fix a code quality or security issue identified by SonarQube.
-
-## Usage
-
-```
-sonar-fix-issue java:S1481 src/main/java/MyClass.java:42
-sonar-fix-issue python:S2077 src/auth/login.py
-sonar-fix-issue Remove unused variable in MyClass.java
-```
-
-## Instructions
-
-### Step 1: Identify the issue
-
-Parse the user-provided arguments for:
-- A rule key (e.g. `java:S1481`, `python:S2077`)
-- A file path and optional line number (e.g. `src/auth/login.py:34`)
-- Or a plain-language description if no rule key is given
-
-If neither a rule key nor a file path can be determined, ask: *"Which rule and file should I fix?"*
-
-### Step 2: Look up the rule (if a key was given)
-
-Call `mcp__sonarqube__show_rule` with the rule key to retrieve the full rule description,
-rationale, and remediation guidance before touching any code. **Do not add extra parameters** (such as `projectKey`) unless the tool schema requires them — after integration, rule lookup usually needs only the rule key.
-
-If the MCP tool is unavailable, fall back to `sonar api get "/api/rules/show?key=<rule-key>"`. If `sonar` is also unavailable or unauthenticated, rely on built-in knowledge of SonarQube rules.
-
-### Step 3: Read the file
-
-Read the full file content. If a line number was given, focus analysis around that line
-but read the whole file to understand context.
-
-### Step 4: Apply the fix
-
-- Make the **minimal change** that resolves the rule violation
-- Do not refactor surrounding code or fix unrelated issues
-- Preserve existing behaviour — the fix must not change what the code does
-
-### Step 5: Explain the change
-
-After editing, briefly explain:
-- What the violation was
-- Why the rule flags it
-- What was changed and why it resolves the issue
-
-### Step 6: Suggest next steps
-
-- *"Invoke the sonar-analyze skill with `<file>` to confirm no new issues were introduced."*
-- *"Invoke the sonar-list-issues skill with the project key (or `sonar.projectKey` in `sonar-project.properties`) — the CLI always uses `-p`."*
+---
+name: sonar-fix-issue
+description: Fix a specific SonarQube issue in code by rule key and location
+argument-hint: "[rule-key] [file-path:line]"
+allowed-tools: Read, Edit, Bash(sonar:*)
+---
+
+# SonarQube — Fix Issue
+
+Fix a code quality or security issue identified by SonarQube.
+
+## Usage
+
+```
+sonar-fix-issue java:S1481 src/main/java/MyClass.java:42
+sonar-fix-issue python:S2077 src/auth/login.py
+sonar-fix-issue Remove unused variable in MyClass.java
+```
+
+## Instructions
+
+### Step 1: Identify the issue
+
+Parse the user-provided arguments for:
+- A rule key (e.g. `java:S1481`, `python:S2077`)
+- A file path and optional line number (e.g. `src/auth/login.py:34`)
+- Or a plain-language description if no rule key is given
+
+If neither a rule key nor a file path can be determined, ask: *"Which rule and file should I fix?"*
+
+### Step 2: Look up the rule (if a key was given)
+
+Call `mcp__sonarqube__show_rule` with the rule key to retrieve the full rule description,
+rationale, and remediation guidance before touching any code. **Do not add extra parameters** (such as `projectKey`) unless the tool schema requires them — after integration, rule lookup usually needs only the rule key.
+
+If the MCP tool is unavailable, fall back to `sonar api get "/api/rules/show?key=<rule-key>"`. If `sonar` is also unavailable or unauthenticated, rely on built-in knowledge of SonarQube rules.
+
+### Step 3: Read the file
+
+Read the full file content. If a line number was given, focus analysis around that line
+but read the whole file to understand context.
+
+### Step 4: Apply the fix
+
+- Make the **minimal change** that resolves the rule violation
+- Do not refactor surrounding code or fix unrelated issues
+- Preserve existing behaviour — the fix must not change what the code does
+
+### Step 5: Explain the change
+
+After editing, briefly explain:
+- What the violation was
+- Why the rule flags it
+- What was changed and why it resolves the issue
+
+### Step 6: Suggest next steps
+
+- *"Invoke the sonar-analyze skill with `<file>` to confirm no new issues were introduced."*
+- *"Invoke the sonar-list-issues skill with the project key (or `sonar.projectKey` in `sonar-project.properties`) — the CLI always uses `-p`."*

Full technical diff · 1 changed fields

changed `/skill_md_contents`

BEFORE

"---\nname: sonar-fix-issue\ndescription: Fix a specific SonarQube issue in code by rule key and location\nargument-hint: \"[rule-key] [file-path:line]\"\nallowed-tools: Read, Edit, Bash(sonar:*)\n---\n\n# SonarQube — Fix Issue\n\nFix a code quality or security issue identified by SonarQube.\n\n## Usage\n\n```\nsonar-fix-issue java:S1481 src/main/java/MyClass.java:42\nsonar-fix-issue python:S2077 src/auth/login.py\nsonar-fix-issue Remove unused variable in MyClass.java\n```\n\n## Instructions\n\n### Step 1: Identify the issue\n\nParse the user-provided arguments for:\n- A rule key (e.g. `java:S1481`, `python:S2077`)\n- A file path and optional line number (e.g. `src/auth/login.py:34`)\n- Or a plain-language description if no rule key is given\n\nIf neither a rule key nor a file path can be determined, ask: *\"Which rule and file should I fix?\"*\n\n### Step 2: Look up the rule (if a key was given)\n\nCall `mcp__sonarqube__show_rule` with the rule key to retrieve the full rule description,\nrationale, and remediation guidance before touching any code. **Do not add extra parameters** (such as `projectKey`) unless the tool schema requires them — after integration, rule lookup usually needs only the rule key.\n\nIf the MCP tool is unavailable, fall back to `sonar api get \"/api/rules/show?key=<rule-key>\"`. If `sonar` is also unavailable or unauthenticated, rely on built-in knowledge of SonarQube rules.\n\n### Step 3: Read the file\n\nRead the full file content. If a line number was given, focus analysis around that line\nbut read the whole file to understand context.\n\n### Step 4: Apply the fix\n\n- Make the **minimal change** that resolves the rule violation\n- Do not refactor surrounding code or fix unrelated issues\n- Preserve existing behaviour — the fix must not change what the code does\n\n### Step 5: Explain the change\n\nAfter editing, briefly explain:\n- What the violation was\n- Why the rule flags it\n- What was changed and why it resolves the issue\n\n### Step 6: Suggest next steps\n\n- *\"Invoke the sonar-analyze skill with `<file>` to confirm no new issues were introduced.\"*\n- *\"Invoke the sonar-list-issues skill with the project key (or `sonar.projectKey` in `sonar-project.properties`) — the CLI always uses `-p`.\"*\n"

AFTER

"---\r\nname: sonar-fix-issue\r\ndescription: Fix a specific SonarQube issue in code by rule key and location\r\nargument-hint: \"[rule-key] [file-path:line]\"\r\nallowed-tools: Read, Edit, Bash(sonar:*)\r\n---\r\n\r\n# SonarQube — Fix Issue\r\n\r\nFix a code quality or security issue identified by SonarQube.\r\n\r\n## Usage\r\n\r\n```\r\nsonar-fix-issue java:S1481 src/main/java/MyClass.java:42\r\nsonar-fix-issue python:S2077 src/auth/login.py\r\nsonar-fix-issue Remove unused variable in MyClass.java\r\n```\r\n\r\n## Instructions\r\n\r\n### Step 1: Identify the issue\r\n\r\nParse the user-provided arguments for:\r\n- A rule key (e.g. `java:S1481`, `python:S2077`)\r\n- A file path and optional line number (e.g. `src/auth/login.py:34`)\r\n- Or a plain-language description if no rule key is given\r\n\r\nIf neither a rule key nor a file path can be determined, ask: *\"Which rule and file should I fix?\"*\r\n\r\n### Step 2: Look up the rule (if a key was given)\r\n\r\nCall `mcp__sonarqube__show_rule` with the rule key to retrieve the full rule description,\r\nrationale, and remediation guidance before touching any code. **Do not add extra parameters** (such as `projectKey`) unless the tool schema requires them — after integration, rule lookup usually needs only the rule key.\r\n\r\nIf the MCP tool is unavailable, fall back to `sonar api get \"/api/rules/show?key=<rule-key>\"`. If `sonar` is also unavailable or unauthenticated, rely on built-in knowledge of SonarQube rules.\r\n\r\n### Step 3: Read the file\r\n\r\nRead the full file content. If a line number was given, focus analysis around that line\r\nbut read the whole file to understand context.\r\n\r\n### Step 4: Apply the fix\r\n\r\n- Make the **minimal change** that resolves the rule violation\r\n- Do not refactor surrounding code or fix unrelated issues\r\n- Preserve existing behaviour — the fix must not change what the code does\r\n\r\n### Step 5: Explain the change\r\n\r\nAfter editing, briefly explain:\r\n- What the violation was\r\n- Why the rule flags it\r\n- What was changed and why it resolves the issue\r\n\r\n### Step 6: Suggest next steps\r\n\r\n- *\"Invoke the sonar-analyze skill with `<file>` to confirm no new issues were introduced.\"*\r\n- *\"Invoke the sonar-list-issues skill with the project key (or `sonar.projectKey` in `sonar-project.properties`) — the CLI always uses `-p`.\"*\r\n"

Full snapshot data

{
  "description": "Fix a specific SonarQube issue in code by rule key and location",
  "included_files": [],
  "name": "sonar-fix-issue",
  "skill_md_contents": "---\r\nname: sonar-fix-issue\r\ndescription: Fix a specific SonarQube issue in code by rule key and location\r\nargument-hint: \"[rule-key] [file-path:line]\"\r\nallowed-tools: Read, Edit, Bash(sonar:*)\r\n---\r\n\r\n# SonarQube — Fix Issue\r\n\r\nFix a code quality or security issue identified by SonarQube.\r\n\r\n## Usage\r\n\r\n```\r\nsonar-fix-issue java:S1481 src/main/java/MyClass.java:42\r\nsonar-fix-issue python:S2077 src/auth/login.py\r\nsonar-fix-issue Remove unused variable in MyClass.java\r\n```\r\n\r\n## Instructions\r\n\r\n### Step 1: Identify the issue\r\n\r\nParse the user-provided arguments for:\r\n- A rule key (e.g. `java:S1481`, `python:S2077`)\r\n- A file path and optional line number (e.g. `src/auth/login.py:34`)\r\n- Or a plain-language description if no rule key is given\r\n\r\nIf neither a rule key nor a file path can be determined, ask: *\"Which rule and file should I fix?\"*\r\n\r\n### Step 2: Look up the rule (if a key was given)\r\n\r\nCall `mcp__sonarqube__show_rule` with the rule key to retrieve the full rule description,\r\nrationale, and remediation guidance before touching any code. **Do not add extra parameters** (such as `projectKey`) unless the tool schema requires them — after integration, rule lookup usually needs only the rule key.\r\n\r\nIf the MCP tool is unavailable, fall back to `sonar api get \"/api/rules/show?key=<rule-key>\"`. If `sonar` is also unavailable or unauthenticated, rely on built-in knowledge of SonarQube rules.\r\n\r\n### Step 3: Read the file\r\n\r\nRead the full file content. If a line number was given, focus analysis around that line\r\nbut read the whole file to understand context.\r\n\r\n### Step 4: Apply the fix\r\n\r\n- Make the **minimal change** that resolves the rule violation\r\n- Do not refactor surrounding code or fix unrelated issues\r\n- Preserve existing behaviour — the fix must not change what the code does\r\n\r\n### Step 5: Explain the change\r\n\r\nAfter editing, briefly explain:\r\n- What the violation was\r\n- Why the rule flags it\r\n- What was changed and why it resolves the issue\r\n\r\n### Step 6: Suggest next steps\r\n\r\n- *\"Invoke the sonar-analyze skill with `<file>` to confirm no new issues were introduced.\"*\r\n- *\"Invoke the sonar-list-issues skill with the project key (or `sonar.projectKey` in `sonar-project.properties`) — the CLI always uses `-p`.\"*\r\n"
}

SHA-256 of public snapshot: 0baa7af0e3135353d556051a9a0dbf2fc1409fb1e1ea0da0d80596e2cb7c41ca