java-debugging

Diagnose Java test failures and flaky behavior with symbol-level navigation.

4|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/Hellblazer/nexus --skill java-debugging
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: java-debugging
Source: https://github.com/Hellblazer/nexus/tree/main/nx/skills/java-debugging
Command: npx skills add https://github.com/Hellblazer/nexus --skill java-debugging

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnoses and resolves Java test failures, exceptions, and non-deterministic behavior by guiding a structured debugging workflow with symbol-aware navigation and root-cause analysis.

Core Features & Use Cases

  • Code Navigation: Use nx:serena-code-nav for symbol-level navigation during debugging to trace calls and locate definitions.
  • Debugging Workflow: A six-step process to form hypotheses, collect evidence, and validate fixes using the java-debugger agent.
  • When This Skill Activates: Triggers on test failures, unexpected exceptions, non-deterministic results, or when the user requests debugging assistance.
  • Agent Invocation: Use the Task tool to invoke the java-debugger agent and generate a root-cause analysis with a recommended fix.

Quick Start

Launch the java-debugging workflow by triggering the java-debugger agent against a failing test to obtain a root cause and suggested fix.

Frequently Asked Questions about java-debugging

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

FAQPage Schema
How do I debug flaky Java tests and non-deterministic failures?

Java debugging of flaky tests uses an agent-assisted workflow with symbol navigation and root-cause analysis to identify non-deterministic failures. It guides a structured six-step process to form hypotheses, collect evidence, and validate fixes.

What's the best way to find the root cause of a Java NullPointerException?

Root-cause analysis for Java exceptions applies symbol-level navigation to trace calls and locate definitions during debugging. It invokes the java-debugger agent to generate a root cause and recommended fix for null-pointer scenarios.

How does symbol navigation work when resolving Java test failures?

Symbol navigation during Java debugging uses Serena-based tooling to trace call paths and locate definitions across Java projects. This code navigation enables precise root-cause analysis by mapping failing test behavior to specific symbol definitions.

Can I use this workflow to diagnose unexpected exceptions across any Java project?

Yes, this Java debugging workflow triggers on unexpected exceptions, test failures, and non-deterministic results across Java projects. It applies structured debugging using agent invocation to diagnose and resolve failures regardless of project structure.

Do I need a specific agent to run the Java debugging workflow?

The Java debugging workflow requires the java-debugger agent and Serena-based navigation tooling for call traces. It uses the Task tool to invoke the agent against failing tests, generating root-cause analysis with suggested fixes.

What steps are involved in the structured Java debugging process?

The Java debugging workflow follows a six-step process to form hypotheses, collect evidence, and validate fixes. It integrates with the nx store for knowledge capture, ensuring debugging evidence and resolutions are documented.