Agent Skills › DetachHead/rebased › debugging

debugging

GitHub

提供IntelliJ开发调试技巧，涵盖日志分析、冻结排查及异常分类。指导通过idea.log搜索日志，并强调从入口端到执行器的全链路追踪与验证方法，用于解决IDE问题或调查失败。

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

Trigger Scenarios

调试IntelliJ插件或代码排查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/.agents/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