serena-jetbrains-workflow

Operates Serena MCP with the JetBrains backend for semantic code exploration, refactoring, and diagnostics.

Updated Jul 20, 2026
One-click install
npx skills add https://github.com/369sup/support --skill serena-jetbrains-workflow-369sup
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: serena-jetbrains-workflow
Source: https://github.com/369sup/support/tree/main/plugins/serena-jetbrains/skills/serena-jetbrains-workflow
Command: npx skills add https://github.com/369sup/support --skill serena-jetbrains-workflow-369sup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Symbol-sensitive coding work requires accurate semantic understanding of declarations, references, and type hierarchies, which plain text search cannot provide. This Skill standardizes how an AI agent connects to Serena MCP with the JetBrains language backend, verifies the integration is actually working, and falls back safely when it is degraded. ## Core Features & Use Cases - Readiness Verification: Activates the project, checks configuration, and runs a real semantic smoke test to classify the integration as READY, DEGRADED, or UNAVAILABLE before relying on it. - Semantic Exploration and Editing: Uses JetBrains-backed declarations, references, implementations, inspections, and refactorings such as rename, move, inline, and safe delete for symbol-sensitive changes. - Integration Diagnosis: Verifies each layer separately, from the Serena CLI and backend configuration to the JetBrains plugin, MCP client, and tool calls, reporting the exact failing boundary. - Use Case: When asked to rename a core service class across a large codebase, the agent confirms the JetBrains semantic backend is live, finds all references, applies a reference-aware rename, checks diagnostics, and reviews the diff. ## Quick Start Use Serena with the JetBrains backend to find all references to this function and rename it safely across the project.

Frequently Asked Questions about serena-jetbrains-workflow

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

FAQPage Schema
How do I use Serena MCP with a JetBrains IDE for code navigation?▼

Activate the project root with activate_project, confirm the JetBrains backend via get_current_config, then use jet_brains_* tools for declarations, references, and implementations. The same project root must be open and indexed in the JetBrains IDE.

How do I verify the Serena JetBrains integration is working?▼

Run one small jet_brains_* semantic read against a real file in the active project. A successful call classifies the integration as READY; configuration checks, open ports, or log lines alone do not prove semantic capability.

What happens when Serena JetBrains semantic tools fail?▼

The integration is classified as DEGRADED or UNAVAILABLE, the exact failed boundary is reported, and the narrowest text or file fallback is used. The same failing operation is not retried repeatedly, and results are not presented as semantically verified.

Can I change the Serena language backend without restarting?▼

No. The language backend is fixed when Serena starts, so the MCP server must be restarted to switch backends. Use one shared monorepo root or separate server sessions for different project roots.

When should Serena semantic tools not be used?▼

Skip the readiness sequence for prose, configuration, generated content, or any task where symbol identity cannot affect the result. Text or file tools are the right choice for questions the semantic backend cannot answer.