---

name: jetbrains-coding description: Use when JetBrains MCP tools are available (mcp__jetbrains__*) - enforces IDE-native workflow with problem checking after file completion, and smart refactoring tools instead of grep/sed

JetBrains IDE-Native Coding

Overview

When JetBrains MCP tools are available, use them instead of Bash/grep/sed. The IDE provides smarter refactoring, real-time error detection, and code formatting that understands your project.

Trigger: MCP tools starting with mcp__jetbrains__ are available.

Mandatory Workflow

CopyEDIT → FILE COMPLETE → CHECK PROBLEMS → FIX → (repeat until 0 problems)

1. After completing a file: Call get_file_problems
2. If problems found: Fix them, check again
3. Continue until: 0 errors/warnings

Tool Preference

When to use standard tools: Non-code files, complex shell pipelines, operations without JetBrains equivalent.

Available Tools (Quick Reference)

Code Intelligence

File Operations

Search

Navigation

Execution

VCS

Debugging

Renaming Files

When renaming files (e.g., task.service.ts → service.ts):

1. Check if IDE has file rename: Some JetBrains MCP versions expose file rename that updates imports automatically
2. If not available: Use git mv for rename, then update imports with replace_text_in_file using replaceAll: true
3. After renaming: ALWAYS run type-check to catch missed imports

Key insight: rename_refactoring is for SYMBOLS (classes, functions, variables), not files. For file renames, you need to update import paths separately.

Common Mistakes

projectPath Parameter

Always pass projectPath to JetBrains tools:

CopyprojectPath: "/absolute/path/to/project"

This avoids ambiguity when multiple projects are open.