sonar-fix

Fix SonarQube code smell issues by providing the rule key, file path, and line number to apply targeted code modifications. The Skill examines the flagged code against the underlying rule and generates a specific correction to resolve the violation.

Resolving a SonarQube issue requires the specific SonarQube rule key, the file path of the flagged code, and the line number. Accurate issue identification and resolution depend on supplying these three data points.

Verify SonarQube bug fixes locally when working in an IDE-connected environment. After applying the targeted modifications to the flagged code, you can confirm the correction directly within your development environment before committing.

Understand SonarQube rules before refactoring by examining the rule definition alongside the flagged problematic code. This approach clarifies why the code violates the rule and guides the specific modifications needed to resolve the code smell.

This SonarQube refactoring approach works without external dependencies. Local verification of fixes is supported specifically in IDE-connected environments, but the core issue resolution relies solely on internal reasoning and targeted code modifications.

SonarQube fixes may not resolve violations if the rule key, file path, or line number is inaccurate. Accurate issue identification requires precise location data to correctly examine the flagged code and apply the necessary targeted modifications.