How do I install the Fix Sonar skill?

Run npx skillmds@latest add alexisbalayre/fix-sonar in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Fix Sonar safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Fix Sonar?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Fix Sonar free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Fix Sonar?

AlexisBalayre (@alexisbalayre) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Fix Sonar by alexisbalayre — Agent Skill

Name: Fix Sonar
Author: AlexisBalayre

File contents

SonarQube Issue Fixer

This agent automates the identification and resolution of SonarQube issues. It prioritizes high-signal mechanical fixes and structured refactoring for complex rules.

Setup: this skill talks to a SonarQube MCP server. Set SONAR_PROJECT_KEY in .env (see .env.example) to your project's key and enable the server in .claude/settings.local.json. The fix-strategy table below is a starting set of common rules: add the rules your project actually hits and record its systematic false positives.

Operation Modes

1. Status Check (`--status`)

Action: Retrieve all OPEN issues for project ${SONAR_PROJECT_KEY}.
Grouping: Aggregate by Rule ID and Codebase Area (the top-level components or directories of the repo).
Display: Present a summary table showing severity, count, and affected files.

2. Parallel Resolution (`--parallel`)

Batching: Group issues by Rule + Area. Create up to 3 independent batches targeting different files.
Isolation: Dispatch 3 parallel agents with isolation: "worktree".
Workflow: Fix -> format/lint -> typecheck -> test (FORMAT_FIX_CMD, LINT_CMD, TYPECHECK_CMD, TEST_CMD from .claude/project.env; skip an empty key) -> Commit -> Push -> PR.
Constraint: Never mix rules or areas within a single batch to prevent merge conflicts and context bleeding.

3. Targeted Fix (`<rule>` or `<rule> <area>`)

Action: Resolve all instances of a specific rule, optionally restricted to a sub-directory/area.

Fix Strategy & Batching Reference

Rule	Category	Strategy	Batch Size
S3776	Complexity	Extract helpers, early returns, flatten nesting.	1-2 files
S107	Refactor	Group parameters into a single options object.	1 file
S1172	Unused	Remove the unused parameter, or document why the signature must keep it.	3-5 files
S1481	Unused	Remove the unused local variable.	5 files
S1192	Duplication	Extract the repeated string literal into a constant.	3-5 files

Agent Dispatch Template

Each parallel agent is initialized with the following instruction set:

"Fix [COUNT] instances of SonarQube rule [RULE] in [AREA]. Context: Refer to [FILE:LINE] list. Verification: Run the project's format/lint, typecheck, and test commands (FORMAT_FIX_CMD, LINT_CMD, TYPECHECK_CMD, TEST_CMD in .claude/project.env). Commit: fix: resolve SonarQube [RULE] [DESCRIPTION] in [AREA]"

Exclusions & Constraints

Auto-generated Files: Skip paths matching GENERATED_PATHS_REGEX in .claude/project.env, and any build output directories (dist/, build/, target/).
Rule Mixing: Under no circumstances should one PR contain fixes for multiple SonarQube rules.

---name: fix-sonardescription: Orchestrate SonarQube issue resolution across the project using parallel agents and specific fix strategies.---# SonarQube Issue FixerThis agent automates the identification and resolution of SonarQube issues. It prioritizes high-signal mechanical fixes and structured refactoring for complex rules.> **Setup:** this skill talks to a SonarQube MCP server. Set `SONAR_PROJECT_KEY` in `.env`> (see `.env.example`) to your project's key and enable the server in> `.claude/settings.local.json`. The fix-strategy table below is a starting set of common> rules: add the rules your project actually hits and record its systematic false positives.## Operation Modes### 1. Status Check (`--status`)- **Action:** Retrieve all `OPEN` issues for project `${SONAR_PROJECT_KEY}`.- **Grouping:** Aggregate by **Rule ID** and **Codebase Area** (the top-level components or directories of the repo).- **Display:** Present a summary table showing severity, count, and affected files.### 2. Parallel Resolution (`--parallel`)- **Batching:** Group issues by Rule + Area. Create up to 3 independent batches targeting different files.- **Isolation:** Dispatch 3 parallel agents with `isolation: "worktree"`.- **Workflow:** Fix -> format/lint -> typecheck -> test (`FORMAT_FIX_CMD`, `LINT_CMD`, `TYPECHECK_CMD`, `TEST_CMD` from `.claude/project.env`; skip an empty key) -> Commit -> Push -> PR.- **Constraint:** Never mix rules or areas within a single batch to prevent merge conflicts and context bleeding.### 3. Targeted Fix (`<rule>` or `<rule> <area>`)- **Action:** Resolve all instances of a specific rule, optionally restricted to a sub-directory/area.## Fix Strategy & Batching Reference| Rule | Category | Strategy | Batch Size || :-------- | :--------- | :------------------------------------------------------ | :--------- || **S3776** | Complexity | Extract helpers, early returns, flatten nesting. | 1-2 files || **S107** | Refactor | Group parameters into a single options object. | 1 file || **S1172** | Unused | Remove the unused parameter, or document why the signature must keep it. | 3-5 files || **S1481** | Unused | Remove the unused local variable. | 5 files || **S1192** | Duplication | Extract the repeated string literal into a constant. | 3-5 files |## Agent Dispatch TemplateEach parallel agent is initialized with the following instruction set:> "Fix [COUNT] instances of SonarQube rule [RULE] in [AREA].> **Context:** Refer to [FILE:LINE] list.> **Verification:** Run the project's format/lint, typecheck, and test commands (`FORMAT_FIX_CMD`, `LINT_CMD`, `TYPECHECK_CMD`, `TEST_CMD` in `.claude/project.env`).> **Commit:** `fix: resolve SonarQube [RULE] [DESCRIPTION] in [AREA]`"## Exclusions & Constraints- **Auto-generated Files:** Skip paths matching `GENERATED_PATHS_REGEX` in `.claude/project.env`, and any build output directories (`dist/`, `build/`, `target/`).- **Rule Mixing:** Under no circumstances should one PR contain fixes for multiple SonarQube rules.

Frequently asked questions

Fix Sonar