How does this skill handle Sonar findings?

It uses predefined standards to apply @SuppressWarnings("java:Sxxxx") or // NOSONAR comments based on the severity and context of the finding.

Can it handle code generated by other tools?

Yes, it includes specific rules to automatically accept findings within generated code directories to avoid unnecessary modifications.

Does it automatically fix all Java errors?

It prioritizes fixing Blocker and Critical issues. For Major, Minor, or Info issues, it evaluates whether to fix, suppress with justification, or accept the finding.

When is this skill triggered during the development process?

It is automatically loaded during the plan-finalize phase when the system detects Java-related build failures, Sonar reports, or linting issues.

What standards does this skill follow?

It adheres to Java-specific suppression syntax and severity guidelines defined in the Plan-Marshall standards library.

Java Issue Triage Extension

Name: Java Issue Triage Extension
Author: cuioss

bycuioss

Security & Testing

Triages Java-related findings and static analysis issues during the finalization phase of the AI coding workflow.

About

The Java Triage Extension for Plan-Marshall provides Claude Code with domain-specific knowledge to intelligently handle Java code issues identified during build, test, or analysis phases. It automates the decision-making process for whether to fix a bug, suppress a warning using standard Java annotations like @SuppressWarnings or NOSONAR, or accept a finding based on severity guidelines. By integrating with Sonar and standard Java linting tools, it ensures that AI-generated code meets production standards while reducing manual review overhead for common false positives and legacy code patterns.

Key Features

Deep integration with Sonar analysis, PR reviews, and build/test outputs
0 GitHub stars
Standardized Java suppression handling for Sonar, deprecations, and unchecked casts
Automated justification generation for suppressed findings
Context-aware triage for generated code and legacy patterns
Severity-based decision logic ranging from Blocker to Info levels

Use Cases

Automating the resolution of SonarQube findings in Java projects
Filtering and triaging false positives in generated Java code during CI/CD
Managing Java warning suppressions during AI-driven code refactoring

About

Key Features

Deep integration with Sonar analysis, PR reviews, and build/test outputs
0 GitHub stars
Standardized Java suppression handling for Sonar, deprecations, and unchecked casts
Automated justification generation for suppressed findings
Context-aware triage for generated code and legacy patterns
Severity-based decision logic ranging from Blocker to Info levels

Use Cases

Automating the resolution of SonarQube findings in Java projects
Filtering and triaging false positives in generated Java code during CI/CD
Managing Java warning suppressions during AI-driven code refactoring