java-healthlisted

Run a comprehensive health check on the Java code or project I've indicated. This is an aggregating command — it runs multiple review dimensions and produces a single scored report. ## Step 1 — Detect context - Check `pom.xml` or `build.gradle` for: Java version, Spring Boot version, dependencies - If a specific file is provided, scope the review to that file - If no file is provided, review the overall project structure ## Step 2 — Run all dimensions in parallel (mentally) Assess each dimension independently, then score it: ### A. Security (0–25 points) Check for: - Hardcoded secrets or credentials (-5 each, max -15) - SQL string concatenation (-5 each, max -10) - Missing input validation on controller methods (-3 each, max -9) - Weak password hashing (MD5/SHA-1) (-8) - Sensitive data in logs (-4) Full score = 25. Deduct per finding. ### B. Test Structure Assessment (0–25 points) > **Note:** This is a *structural* assessment — Claude cannot run your test suite or measure real line coverage. For actual coverage numbers run `mvn test jacoco:report` or `./gradlew test jacocoTestReport`. Check for: - Presence of test files for each service class (-5 per missing service test, max -15) - Use of H2 instead of Testcontainers for DB integration tests (-5) - Missing exception path tests (no test method with "throws", "exception", or "notFound" in name) (-3 per service class, max -9) - Tests that mock the class under test (-4) Full score = 25. Deduct per finding. ### C. Perfo