Skill

Step 1 — Identify the error type

Diagnoses and fixes Java compile errors, runtime exceptions, and stack traces from javac, Maven, or Gradle. Useful when users report 'fix this error', 'won't compile', or 'debug this'.

Java

backend

code-quality

npx claudepluginhub ducpm2303/claude-java-plugins --plugin java-core

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Diagnose the Java error or stack trace I've provided and propose a fix. Be specific — do not give generic advice.

SKILL.md

Similar Skills

fix

Quickly diagnoses and fixes simple errors from stack traces and messages, including syntax errors, import issues, build failures, failing tests, and lint errors.

claude-code-starter

debugger

682

Debugs errors, test failures, and unexpected behavior through root cause analysis, stack trace review, hypothesis testing, logging, and targeted code fixes.

rmyndharis-antigravity-skills

dev-debug

963

Categorizes and debugs compile/type errors, failing tests, runtime exceptions, env/setup issues, lint violations, deps conflicts, and webtest failures with minimal context.

tsumiki

Stats

Parent Repo Stars13

Parent Repo Forks0

Last CommitApr 3, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Diagnose the Java error or stack trace I've provided and propose a fix. Be specific — do not give generic advice.

Step 1 — Identify the error type

Compile errors (javac / Maven / Gradle output):

cannot find symbol → missing import, misspelled name, or wrong scope
incompatible types → type mismatch; check generics, autoboxing, widening
method X is not applicable → wrong number or types of arguments
variable X might not have been initialized → missing initialisation on all code paths
reached end of file while parsing → unmatched { or }
class X is public, should be declared in a file named X.java → filename mismatch

Runtime exceptions (stack traces):

NullPointerException → identify the line; determine which reference is null; suggest a null check or Optional
ClassCastException → show the actual vs expected type; fix the cast or use instanceof first
ArrayIndexOutOfBoundsException → check loop bounds and array length
StackOverflowError → identify the recursive call; check base case
ConcurrentModificationException → iterating and modifying a collection simultaneously; suggest iterator.remove() or a copy
IllegalArgumentException / IllegalStateException → read the message; check the API contract

Step 2 — Find the root cause

Read the full error message carefully. The root cause is usually the last "Caused by:" in a stack trace. Show the user:

The exact line causing the error (if visible in the stack trace)
Why that line fails

Step 3 — Propose the fix

Show:

The problematic code (before)
The corrected code (after)
One sentence explaining what was wrong

If the fix requires reading a file not currently shown, ask for it: "Can you share the contents of ClassName.java? I need to see [specific thing]."

Step 4 — Prevent recurrence

Add one short note on how to avoid this class of error in the future (e.g., "Use Objects.requireNonNull() at method entry to catch nulls early").

Next Steps

After applying the fix:

Suggest running the build to verify: mvn compile -q or ./gradlew build -q
If the fix changed business logic → suggest running /java-test to verify behaviour is preserved
If the root cause was a design problem → suggest running /java-review on the surrounding code