Agent Skills
› DetachHead/rebased
› debugging
debugging
GitHub提供 IntelliJ IDE 调试技巧，包括日志搜索模式和端到端行为追踪方法，帮助定位代码问题。
Trigger Scenarios
IntelliJ IDE 运行异常
IDE 界面卡顿或无响应
需要分析特定类的日志输出
Install
npx skills add DetachHead/rebased --skill debugging -g -y
SKILL.md
Frontmatter
{
"name": "debugging",
"description": "Debug IntelliJ IDE failures with repository-specific techniques."
}
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 (fromLOG.debug { })INFO= info level (fromLOG.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
Version History
- 2af32ff Current 2026-09-22 01:02
- 1f8708d 2026-08-16 15:38
