debugging

Diagnose IntelliJ IDE issues through log analysis and exception tracing.

20.4k|6.0k|Updated Sep 30, 2011
One-click install
npx skills add https://github.com/JetBrains/intellij-community --skill debugging-jetbrains
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debugging
Source: https://github.com/JetBrains/intellij-community/tree/main/.agents/skills/debugging
Command: npx skills add https://github.com/JetBrains/intellij-community --skill debugging-jetbrains

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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

Core Features & Use Cases

  • Documentation references: Logger FAQ, How to Investigate Freezes, Exception Analyzing FAQ to guide diagnosis.
  • Log analysis: Searching idea.log by log levels and class patterns to locate relevant issues.
  • End-to-End Behavior: A structured approach to trace the full execution chain from an entry point to the actual executor, including recommended debugging outputs.

Quick Start

Start by identifying the failing IDE area and follow the end-to-end debugging steps to reproduce and trace the issue.

Frequently Asked Questions about debugging

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug IntelliJ IDE freezes and exceptions?

To debug IntelliJ IDE freezes and exceptions, use a structured end-to-end approach to trace the execution chain from entry point to executor. This workflow leverages documentation like the Logger FAQ and Exception Analyzing FAQ to guide your diagnosis.

How do I search idea.log to locate IntelliJ Platform issues?

You search idea.log to locate IntelliJ Platform issues by filtering entries based on specific log levels and class patterns. This log analysis isolates relevant exceptions and errors documented within the IDE's diagnostic output.

What is the end-to-end behavior approach for troubleshooting IntelliJ codebase failures?

The end-to-end behavior approach for troubleshooting IntelliJ codebase failures is a structured method to trace the full execution chain from an entry point to the actual executor. It includes recommended debugging outputs to systematically reproduce and investigate the failure.

Does this debugging workflow require specific dependencies or components?

No, this debugging workflow does not require specific dependencies or components to function. It provides structured guidance and documented resources for diagnosing IntelliJ Platform codebase issues without external setup requirements.

What is the best way to investigate IDE issues in the IntelliJ Platform codebase?

The best way to investigate IDE issues in the IntelliJ Platform codebase is to identify the failing area first, then follow end-to-end debugging steps to reproduce and trace the issue. This process utilizes documented resources for analyzing freezes, exceptions, and log patterns.