OpenParable
Skip to content
← Back to skills

Debugging

Testing & Quality
debugging

Debugging is an Agent Skill for testing & quality published in the JetBrains/intellij-community repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Debugging techniques and tools for IntelliJ development. Use when debugging IDE issues or investigating failures.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/JetBrains/intellij-community/blob/HEAD/.claude/skills/debugging/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/debugging, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Debugging

Documentation

Searching idea.log

When debugging IntelliJ code, search idea.log using these patterns:

Log Levels:

  • FINE = debug level (from LOG.debug { })
  • INFO = info level (from LOG.info())

Category Format: #<abbreviated.package.path>.<ClassName>

Example: com.intellij.openapi.wm.impl.status.IdeStatusBarImpl → #c.i.o.w.i.s.IdeStatusBarImpl

Search Examples:

# Debug logs from IdeStatusBarImpl
grep "FINE - #c.i.o.w.i.s.IdeStatusBarImpl" idea.log

# Info logs from IdeStatusBarImpl
grep "INFO - #c.i.o.w.i.s.IdeStatusBarImpl" idea.log

# All logs from a class
grep "#c.i.o.w.i.s.IdeStatusBarImpl" idea.log

End-to-End Behavior

When fixing issues where a user-facing entry point (script, command, API) doesn't behave as expected:

  1. Trace the full execution chain from entry point to actual executor before making changes
  2. Identify all layers that handle the relevant behavior - each layer may swallow, transform, or ignore it
  3. Verify the fix at the entry point the user actually invokes, not just at the layer you modified
  4. Add debugging output if still unsure - add to all layers to trace the issue