java-project-health

Run a Java project health check by invoking the skill to execute universal checks first, then Java-specific validations across architecture, dependencies, and code quality. It analyzes pom.xml or build.gradle files alongside source and test directories to produce actionable findings.

Project health checking works with both Maven and Gradle by scanning build configuration files like pom.xml and build.gradle. It validates dependency alignment and architecture integrity across Java projects regardless of the specific build tool used.

A Java project health check covers architecture integrity, dependency alignment, and code-quality signals across source, tests, and configuration files. It applies tiered checks to scan targets including src/main/java, src/test/java, and resources to identify project health issues.

You can check code quality across source and test directories by running tiered health checks that scan src/main/java and src/test/java. The skill evaluates code-quality signals and configuration files to produce standardized output formatting with actionable guidance.

The best way to identify dependency alignment issues is running an automated health check that validates build configurations like pom.xml and build.gradle. The skill applies tiered checks to detect dependency misalignment and generates standardized output with corrective guidance.

Your Java project health check includes universal checks to establish a baseline of project health before applying Java-specific validations. It runs universal project-health checks first, then adds targeted checks for architecture integrity, dependency alignment, and code quality.