Agent Skills › DetachHead/rebased › debugging

debugging

GitHub

提供 IntelliJ IDE 调试技巧，涵盖 idea.log 搜索模式、日志级别解析及端到端行为追踪方法，辅助排查冻结、异常和入口点故障。

.claude/skills/debugging/SKILL.md DetachHead/rebased

Trigger Scenarios

IDE 运行卡顿或冻结分析代码执行异常排查用户入口点功能故障

Install

npx skills add DetachHead/rebased --skill debugging -g -y

More Options

Non-standard path

npx skills add https://github.com/DetachHead/rebased/tree/master/.claude/skills/debugging -g -y

Use without installing

npx skills use DetachHead/rebased@debugging

指定 Agent (Claude Code)

npx skills add DetachHead/rebased --skill debugging -a claude-code -g -y

安装 repo 全部 skill

npx skills add DetachHead/rebased --all -g -y

预览 repo 内 skill

npx skills add DetachHead/rebased --list

SKILL.md

Frontmatter

{
    "name": "debugging",
    "description": "Debugging techniques and tools for IntelliJ development. Use when debugging IDE issues or investigating failures."
}

Debugging

Documentation

Logger FAQ - Frequently asked questions about logging
How to Investigate Freezes - Diagnosing IDE freezes
Exception Analyzing FAQ - Analyzing and categorizing exceptions

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:

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