debugging-playbook

Diagnose Java stack traces in Spring Boot services using Actuator endpoints and JDWP.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/RogerioSobrinho/codeme-copilot --skill debugging-playbook-rogeriosobrinho
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debugging-playbook
Source: https://github.com/RogerioSobrinho/codeme-copilot/tree/main/skills/debugging-playbook
Command: npx skills add https://github.com/RogerioSobrinho/codeme-copilot --skill debugging-playbook-rogeriosobrinho

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Load when reading a Java stack trace to identify root cause, diagnosing a NullPointerException, LazyInitializationException, BeanCreationException, or ContextRefreshException in Spring Boot, using Spring Boot Actuator endpoints (/actuator/env, /actuator/beans, /actuator/conditions, /actuator/loggers) to diagnose a runtime issue, configuring JDWP remote debug for a JVM in Docker, reading a thread dump to find deadlocks or blocked threads, or when asked "how do I debug this", "what does this stack trace mean", "why is the application context not starting", "how do I attach a debugger to this Docker container".

Core Features & Use Cases

  • Stepwise analysis of stack traces to locate the real failure behind framework noise.
  • Actuator-assisted inspection of runtime state (env, beans, conditions, loggers) to pinpoint issues.
  • Guidance for remote debugging in Docker, including thread dumps and common failure scenarios.

Quick Start

Read a Java stack trace and follow the step-by-step guidance to identify root causes and apply debugging tactics.

Frequently Asked Questions about debugging-playbook

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

FAQPage Schema
How do I find the root cause of a Spring Boot BeanCreationException from a long stack trace?

To find the root cause of a BeanCreationException, analyze the Java stack trace step-by-step to bypass Spring framework noise and pinpoint the actual underlying failure. This approach isolates the real initialization error for safe remediation.

How do I attach a JDWP remote debugger to a Java application running in a Docker container?

Configure JDWP remote debugging by modifying your Docker deployment to expose the JVM debugging port. This allows you to attach a debugger to the containerized Spring Boot service and inspect the runtime state directly.

What Spring Boot Actuator endpoints help diagnose why my application context is not starting?

Use Spring Boot Actuator endpoints like /actuator/env, /actuator/beans, and /actuator/conditions to inspect the runtime state. These endpoints reveal environment configurations and bean creation issues that prevent the application context from starting.

How do I read a thread dump to find deadlocks or blocked threads in a JVM?

Read a thread dump to identify deadlocks or blocked threads by analyzing the JVM stack traces of concurrent threads. The process highlights thread states and lock contentions, guiding you through resolving thread deadlocks in Spring Boot services.

Can I use this debugging guidance for a LazyInitializationException in a cloud deployment?

Yes, this debugging guidance applies to JVM-based Spring Boot services in Docker or cloud deployments. It provides actionable steps to diagnose and safely remediate LazyInitializationException scenarios across these environments.

What is the best way to debug a NullPointerException hidden behind framework noise in Java?

The best way to debug a NullPointerException hidden by framework noise is performing a stepwise analysis of the Java stack trace. This method focuses on the actual failure deeper than the framework layers to provide actionable debugging steps.