Claude Idea Debug Skill — Testing skill for Claude Code

idea-debug

A [Claude Code](https://docs.claude.com/en/docs/claude-code/overview) skill that triggers an IntelliJ IDEA test/debug run from your Claude conversation, captures the console log and JUnit results, and pipes them back to Claude for analysis.

**Platform:** Windows only (uses Win32 API + PowerShell + `wscript.exe`).

What it does

You're in Claude Code, you've been editing Java code in IntelliJ. You type:

/idea-debug

Behind the scenes, the skill:

1. Brings IntelliJ to the foreground.
2. Sends Debug shortcut (default is Shift+F9, re-run last config — works for both run and debug).
3. Waits for the test-runner JVM to exit (no timeout, with a 10s heartbeat for long suites).
4. Reads the console log file (debug-capture.log) IntelliJ wrote during the run.
5. Parses the JUnit XML and prints [PASS] / [FAIL] per test with stderr.
6. Minimizes IntelliJ so Claude Code surfaces again — without disturbing your Alt+Tab order.

Claude then summarizes pass/fail and suggests fixes based on the captured stack traces.

Why this exists

Triggering IntelliJ from a Claude Code subprocess on Windows runs into several non-obvious quirks (cross-process focus stealing, JVM daemon reuse, key injection from a non-interactive shell, taskbar focus blocks). This skill works around all of them. See [DESIGN-NOTES.md](#design-notes-the-four-windows-quirks-this-skill-works-around) below for the technical details.

Installation

1. Find your Claude Code skills directory (varies by install — search for an existing skills/ folder near your Claude Code data directory).
2. Copy this repo's contents into a folder named idea-debug inside that directory:

   /idea-debug/
   ├── SKILL.md
   └── scripts/
       ├── Debug-And-Capture.ps1
       ├── Chase-DebugProcess.ps1
       └── WinApi.ps1

3. Restart Claude Code so it picks up the new skill.
4. In IntelliJ, open your project's Run/Debug Configuration and add (one-time setup):
   • **Logs t