serena
Serena MCP usage guide for semantic code operations, symbol manipulation, project memory, and session persistence. Use when invoking any mcp__serena__* tools, performing symbol operations (rename, find references, extract), navigating large codebases, or managing project memory/sessions.
What this skill does
# Serena MCP Server
Semantic code understanding with project memory and session persistence.
## Required First Step
**ALWAYS activate project before any Serena operation:**
```
mcp__serena__activate_project(project: "<path_or_name>")
mcp__serena__check_onboarding_performed()
```
## When to Use Serena
| Use Case | Serena | Alternative |
|----------|--------|-------------|
| Symbol rename with references | ✅ | ❌ Morphllm |
| Find all references | ✅ | ❌ Grep |
| Semantic code navigation | ✅ | ❌ Native |
| Project memory/session | ✅ | ❌ None |
| Pattern-based bulk edits | ❌ | ✅ Morphllm |
| Simple text replacement | ❌ | ✅ Edit tool |
## Core Tools
### Project Lifecycle
- `activate_project` → **REQUIRED FIRST** - activate target project
- `get_current_config` → check active project and available tools
- `check_onboarding_performed` → verify project is ready
- `onboarding` → run if onboarding not yet performed
### Symbol Operations
- `find_symbol` → locate symbols by name path pattern
- `find_referencing_symbols` → find all references to a symbol
- `get_symbols_overview` → high-level view of file symbols
- `rename_symbol` → rename across entire codebase
- `replace_symbol_body` → replace symbol definition
- `insert_before_symbol` / `insert_after_symbol` → add code around symbols
### Search & Navigation
- `search_for_pattern` → regex search across codebase
- `list_dir` → list directory contents
- `find_file` → find files by mask
### Memory Management
- `write_memory` → persist information for future sessions
- `read_memory` → retrieve stored information
- `list_memories` → show available memories
- `edit_memory` / `delete_memory` → modify or remove memories
### Reflection (Call These!)
- `think_about_collected_information` → after search operations
- `think_about_task_adherence` → before code modifications
- `think_about_whether_you_are_done` → at task completion
## Tool Details
See [references/tools.md](references/tools.md) for detailed parameter documentation.
## Workflow Patterns
### Session Start
```
1. activate_project(project: "path/to/project")
2. check_onboarding_performed()
3. list_memories() → check existing context
4. read_memory("relevant_memory") → if applicable
```
### Symbol Investigation
```
1. get_symbols_overview(relative_path: "file.py", depth: 1)
2. find_symbol(name_path_pattern: "ClassName", include_body: false)
3. find_symbol(name_path_pattern: "ClassName/method", include_body: true)
4. think_about_collected_information()
```
### Symbol Modification
```
1. find_symbol(name_path_pattern: "target", include_body: true)
2. think_about_task_adherence()
3. replace_symbol_body(name_path: "target", relative_path: "file.py", body: "new code")
```
### Cross-Session Persistence
```
1. write_memory("task_context", "important findings...")
2. [end session]
3. [new session]
4. activate_project(...)
5. list_memories()
6. read_memory("task_context")
```
## Name Path Patterns
| Pattern | Matches |
|---------|---------|
| `method` | Any symbol named "method" |
| `Class/method` | method inside Class |
| `/Class/method` | Exact path from file root |
| `Foo/get` with `substring_matching: true` | `Foo/getValue`, `Foo/getData` |
## Best Practices
1. **Activate first** - Always `activate_project` before operations
2. **Read before edit** - Use `find_symbol` with `include_body: true` before modifications
3. **Use reflection tools** - Call `think_about_*` tools at appropriate points
4. **Prefer symbolic over text** - Use symbol tools over grep/edit when possible
5. **Persist important context** - Use memory for cross-session continuity
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.