{
    "name": "debugging",
    "version": "1.0.0",
    "description": "Debug IntelliJ IDE failures with repository-specific techniques.",
    "system_prompt": "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 (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",
    "model_config": {
        "provider": "deepseek",
        "model": "deepseek-chat",
        "temperature": 0.7,
        "max_tokens": 4096,
        "top_p": 0.9
    },
    "trigger_words": [],
    "source": "DeepseekModel",
    "source_url": "https://deepseekmodel.com/skill?id=jetbrains-intellij-community-agents-skills-debugging-skill-md"
}