java-doctor

Analyze Java projects to produce a 0-100 health score and diagnostics.

41|10|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/ajaywadhara/java-doctor --skill java-doctor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: java-doctor
Source: https://github.com/ajaywadhara/java-doctor/tree/main
Command: npx skills add https://github.com/ajaywadhara/java-doctor --skill java-doctor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Java Doctor provides an AI-driven health analysis for Java projects, delivering a 0-100 score and actionable diagnostics to drive improvements.

Core Features & Use Cases

  • Progressive loading of rules based on detected technologies (Spring, gRPC, JPA) to optimize performance.
  • Automatic technology detection from Maven/Gradle configs and project structure.
  • Comprehensive diagnostics across security, performance, correctness, and architecture with actionable fixes.
  • Version-aware checks for Java 8-25 and Spring Boot 3.x/4.x, including dead code detection.

Quick Start

Install via the Skills CLI, then activate the skill and say Run Java Doctor.

Frequently Asked Questions about java-doctor

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

FAQPage Schema
How do I analyze my Java project's code health and get a diagnostic score?

Java project code health analysis is automated by detecting technologies like Spring and JPA, then loading relevant rules on-demand to deliver a 0-100 health score and actionable diagnostics across security, performance, and architecture.

How does static analysis handle different Java versions and Spring Boot frameworks?

Static analysis provides version-aware checks for Java 8 through 25 and Spring Boot 3.x and 4.x, ensuring that code reviews and diagnostics respect the specific constraints and features of your project's technology stack.

Can I use this to detect dead code and architectural issues in a Maven or Gradle project?

Dead code detection and architectural diagnostics are supported by automatically detecting your Maven or Gradle build configurations and project structure, applying progressively loaded rules to identify unused code and structural improvements.

What is the best way to review Java code for security and performance issues automatically?

Automated Java code review for security and performance issues is handled by analyzing your project to detect technologies like gRPC and Lombok, then applying targeted rules to generate actionable fixes for identified vulnerabilities.

Does Java Doctor work with projects using Lombok and gRPC?

Projects using Lombok and gRPC are fully supported through automatic technology detection from build configs, which triggers the progressive loading of specific static analysis rules tailored to those frameworks.

Why does my Java code review only show generic issues instead of framework-specific diagnostics?

Generic code reviews often lack context, whereas progressive rule loading detects technologies like Spring and JPA from your build tools to provide version-aware, framework-specific diagnostics and targeted architectural improvements.