validate-style-complete

Run Checkstyle, PMD, and manual rules checks on Java projects.

4|Updated Sep 25, 2025
One-click install
npx skills add https://github.com/cowwoc/styler --skill validate-style-complete
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: validate-style-complete
Source: https://github.com/cowwoc/styler/tree/main/.claude/skills/validate-style-complete
Command: npx skills add https://github.com/cowwoc/styler --skill validate-style-complete

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures comprehensive style validation by running Checkstyle, PMD, and manual rules, preventing missed violations.

Core Features & Use Cases

  • Checkstyle: Run mvnw checkstyle:check
  • PMD: Run mvnw pmd:check
  • Manual Rules: Review code-style-human.md for TIER1/TIER2/TIER3 violations
  • Before Completion: Ensure all checks pass before declaring style validation complete.

Quick Start

Run the complete style validation using the supplied script: /workspace/main/.claude/scripts/validate-style-complete.sh

To validate a specific module: /workspace/main/.claude/scripts/validate-style-complete.sh --module formatter

Frequently Asked Questions about validate-style-complete

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run complete style validation on a Java project with Checkstyle, PMD, and manual rules?

Complete style validation runs three components: Checkstyle via mvnw checkstyle:check, PMD via mvnw pmd:check, and manual rules reviewed against code-style-human.md. Execute /workspace/main/.claude/scripts/validate-style-complete.sh to run all checks together and generate a standardized result report before declaring style validation complete.

What does Checkstyle and PMD validation check for in Java code?

Checkstyle and PMD enforce line length, indentation, naming conventions, JavaDoc compliance, import organization, and code complexity rules. These static-analysis tools catch style violations automatically, preventing incomplete style checks and ensuring consistent code standards across your project.

Can I validate style for a specific Maven module instead of the entire project?

Yes, the validate-style-complete.sh script accepts a --module parameter to run validation on individual modules. For example, /workspace/main/.claude/scripts/validate-style-complete.sh --module formatter targets only the formatter module while applying all three validation components.

When should I use comprehensive style validation instead of running Checkstyle or PMD alone?

Comprehensive style validation prevents missed violations by combining automated checks (Checkstyle, PMD) with manual review criteria organized by severity tiers. Use it before declaring completion to ensure no style violations slip through, especially across multiple modules in validation workflows.

What's included in the manual rules review for style validation?

Manual rules are documented in code-style-human.md and organized into TIER1, TIER2, and TIER3 violations based on severity. These criteria catch style issues that automated tools miss, requiring human review to ensure complete compliance before validation completes.

Does this style validation work with multi-module Maven projects?

Yes, the Skill applies across multiple modules in validation workflows. Run the script without --module to validate all modules, or specify --module to target individual ones, ensuring comprehensive style compliance across your entire Maven project structure.