What problem does it solve?
When an XTDB test run, node, or Gradle worker hangs, diagnosing the cause requires capturing and interpreting a Java thread dump — a file containing tens of thousands of tokens of stack traces that is impractical to read directly. This Skill guides the capture of dumps from running Gradle workers and delegates the parsing to a sub-agent so the dump stays out of the main context.
Core Features & Use Cases
- Thread dump capture: Uses jps and jstack to snapshot a running GradleWorkerMain process, with guidance for handling multiple workers.
- Delegated analysis: Sends the dump file path to a cheap-model sub-agent that reports deadlocks, blocked threads, lock contention, thread-state distribution, pool health, and repeated stacks.
- XTDB-aware interpretation: Maps findings onto XTDB subsystems via allocator and executor names, and recommends comparing two dumps taken seconds apart to distinguish livelocks from true deadlocks.
- Use Case: A Gradle test run stops making progress. Capture a dump with jstack, delegate the parse to a sub-agent, and receive a report identifying an exhausted thread pool as the root cause.
Quick Start
Ask the assistant to capture a thread dump from the hung Gradle worker and analyze it for deadlocks and blocked threads.