// Analyze Java source files for code quality issues including style violations, complexity warnings, and common anti-patterns. Use when reviewing Java code, running quality checks, or preparing for code review.
| name | code-quality |
| description | Analyze Java source files for code quality issues including style violations, complexity warnings, and common anti-patterns. Use when reviewing Java code, running quality checks, or preparing for code review. |
| license | Apache-2.0 |
| compatibility | Requires Java 17+ (JEP 330 single-file execution) |
| metadata | {"author":"skillscraft","version":"1.0","category":"code-quality","language":"java"} |
Activate when the user wants to:
java scripts/CheckStyle.java <source-file-or-directory>
java scripts/FindPatterns.java <source-file>
java scripts/CheckStyle.java --rules assets/default-rules.json <path>Scripts output JSON to stdout:
{
"file": "MyClass.java",
"issues": [
{
"line": 15,
"rule": "method-too-long",
"severity": "warning",
"message": "Method 'processData' has 65 lines (max: 50)"
}
],
"summary": { "errors": 0, "warnings": 1, "info": 0 }
}
The default ruleset is in assets/default-rules.json. Copy it and modify thresholds to customize. Key defaults:
.java files only — other file types are skippedbuild/, target/, and hidden directoriesassets/default-rules.json can be modified but the schema must remain unchangedMaintain project health by enforcing PR checklists, tracking open issues, verifying release readiness, and ensuring framework phases are up to date. Use when reviewing PRs, creating issues, preparing releases, or auditing project state.
Scaffold new Agent Skills with best-practice structure and frontmatter. Use when the user wants to create a new skill, bootstrap a skill directory, or generate SKILL.md boilerplate following the Agent Skills spec.
Validate CSV and JSON data files against schemas and quality rules. Use when the user asks to check data quality, validate a dataset, or verify file contents match an expected schema.
Audit project dependencies for known vulnerabilities, outdated packages, and license compliance issues. Use when the user asks to check dependencies, audit packages, review licenses, or assess supply chain security.
Generate friendly greeting messages in multiple languages. Use when the user asks for a hello message, welcome text, or localized greeting.
Maintain project release notes, changelogs, and framework phase updates. Use when the user asks to generate a changelog, draft release notes, update CHANGELOG.md, or track framework phase transitions.