How do I install the Jetbrains Skill skill?

Run npx skillmds@latest add ry-run/jetbrains-skill in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Jetbrains Skill safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Jetbrains Skill?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Jetbrains Skill free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Jetbrains Skill?

ry-run (@ry-run) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Jetbrains Skill by ry-run — Agent Skill

Name: Jetbrains Skill
Author: ry-run

Jetbrains Skill

Use the JetBrains IDE MCP Server (IntelliJ IDEA 2025.2+) for IDE-backed indexing, inspections, symbol info, project file operations, and structural refactoring. Use it when you need exact project-aware analysis or safe IDE refactors, rather than broad semantic repository discovery.

ry-run 6f56b5c 5 files · 17.0 KB Updated Sep 17, 2026

File contents

JetBrains Skill

Quick start

Goal: use JetBrains IDE features (index, inspections, refactoring, run configurations, integrated terminal) as tools for an external client, while keeping changes auditable and safe.

notes + tool list (condensed): skills/jetbrains-skill/references/jetbrains-skill.md.

Connection & modes

Client setup (done in the IDE)

Settings → Tools → MCP Server
Enable MCP Server
Use “Auto-configure” for supported clients (updates their JSON config), or copy SSE / Stdio config for manual setup
Restart the external client to apply changes

Brave Mode (no confirmations)

The IDE can allow running shell commands / run configurations without per-action confirmation (“Brave mode”). This increases automation power but also increases risk. Require explicit user confirmation before enabling/disabling it.

Workflow decision tree

Do I need IDE-grade analysis/refactoring?

File diagnostics: get_file_problems
Symbol semantics / docs: get_symbol_info
Safe rename across project: rename_refactoring (prefer over plain text replace)
Indexed search: search_in_files_by_text / search_in_files_by_regex
Find files: find_files_by_name_keyword (fast, name-only) or find_files_by_glob (path glob)

Do I just need file operations in the project?

Read file text: get_file_text_by_path
Create file: create_new_file
Targeted replace: replace_text_in_file (auto-saves)
Open in editor: open_file_in_editor
Reformat: reformat_file

Do I need to run something?

List run configs: get_run_configurations
Run a config (wait for completion): execute_run_configuration
Run a terminal command in IDE: execute_terminal_command (may require confirmation; output is capped)

Constraints (avoid common mistakes)

Always pass projectPath when known to avoid ambiguity.
Many tools require paths relative to the project root and only operate on project files.
Line/column positions are 1-based for location-based tools.
Prefer controlling output with maxLinesCount + truncateMode; do not rely on defaults for large outputs.
Terminal commands and running configurations are high-risk; require explicit confirmation for any potentially destructive command. Brave Mode removes guardrails.

Recommended high-value patterns

Debug via inspections first

get_file_problems to find errors/warnings → 2) get_symbol_info to understand the code → 3) rename_refactoring for renames → 4) replace_text_in_file only for truly textual changes.

Use indexed search for scale

Prefer search_in_files_by_text / search_in_files_by_regex since it uses IDE search/indexing and highlights matches with ||.

Running and output control

Use execute_run_configuration with a sane timeout (ms). For terminal commands use execute_terminal_command, but remember output caps; for huge output, redirect to a file and read it via file tools.

References

notes + tool list (condensed): skills/jetbrains-skill/references/jetbrains-skill.md

---name: jetbrains-skilldescription: Use the JetBrains IDE MCP Server (IntelliJ IDEA 2025.2+) for IDE-backed indexing, inspections, symbol info, project file operations, and structural refactoring. Use it when you need exact project-aware analysis or safe IDE refactors, rather than broad semantic repository discovery.---# JetBrains Skill## Quick startGoal: use JetBrains IDE features (index, inspections, refactoring, run configurations, integrated terminal) as tools for an external client, while keeping changes auditable and safe.notes + tool list (condensed): `skills/jetbrains-skill/references/jetbrains-skill.md`.## Connection & modes### Client setup (done in the IDE)- Settings → Tools → MCP Server- Enable MCP Server- Use “Auto-configure” for supported clients (updates their JSON config), or copy SSE / Stdio config for manual setup- Restart the external client to apply changes### Brave Mode (no confirmations)The IDE can allow running shell commands / run configurations without per-action confirmation (“Brave mode”).This increases automation power but also increases risk. Require explicit user confirmation before enabling/disabling it.## Workflow decision tree1) Do I need IDE-grade analysis/refactoring?- File diagnostics: `get_file_problems`- Symbol semantics / docs: `get_symbol_info`- Safe rename across project: `rename_refactoring` (prefer over plain text replace)- Indexed search: `search_in_files_by_text` / `search_in_files_by_regex`- Find files: `find_files_by_name_keyword` (fast, name-only) or `find_files_by_glob` (path glob)2) Do I just need file operations in the project?- Read file text: `get_file_text_by_path`- Create file: `create_new_file`- Targeted replace: `replace_text_in_file` (auto-saves)- Open in editor: `open_file_in_editor`- Reformat: `reformat_file`3) Do I need to run something?- List run configs: `get_run_configurations`- Run a config (wait for completion): `execute_run_configuration`- Run a terminal command in IDE: `execute_terminal_command` (may require confirmation; output is capped)## Constraints (avoid common mistakes)- Always pass `projectPath` when known to avoid ambiguity.- Many tools require paths relative to the project root and only operate on project files.- Line/column positions are 1-based for location-based tools.- Prefer controlling output with `maxLinesCount` + `truncateMode`; do not rely on defaults for large outputs.- Terminal commands and running configurations are high-risk; require explicit confirmation for any potentially destructive command. Brave Mode removes guardrails.## Recommended high-value patterns### Debug via inspections first1) `get_file_problems` to find errors/warnings → 2) `get_symbol_info` to understand the code → 3) `rename_refactoring` for renames → 4) `replace_text_in_file` only for truly textual changes.### Use indexed search for scalePrefer `search_in_files_by_text` / `search_in_files_by_regex` since it uses IDE search/indexing and highlights matches with `||`.### Running and output controlUse `execute_run_configuration` with a sane `timeout` (ms). For terminal commands use `execute_terminal_command`, but remember output caps; for huge output, redirect to a file and read it via file tools.## References- notes + tool list (condensed): `skills/jetbrains-skill/references/jetbrains-skill.md`

Frequently asked questions