What problem does it solve? Java projects accumulate stale, unused, or mis-scoped Maven dependencies over time, bloating builds and increasing maintenance risk. This Skill audits pom.xml dependencies against actual source code usage so you can safely clean up your project. ## Core Features & Use Cases - Usage Classification: Categorizes each dependency as actively used, runtime/provider, transitive duplicate, test-only, or potentially unused by scanning imports in src/main/java and src/test/java. - Runtime Dependency Awareness: Recognizes dependencies without direct imports that are still required, such as JDBC drivers, Spring Boot starters, Lombok, and logging backends. - Structured Audit Report: Produces a categorized report with scope-mismatch warnings and removal recommendations, plus verification steps using mvn compile and mvn test. - Use Case: Before a Spring Boot version upgrade, ask for a dependency audit to find unused libraries and dependencies that should be moved to test scope, reducing the upgrade surface. ## Quick Start Analyze the dependencies in my pom.xml and tell me which ones are unused or should have their scope changed.
