semantic-code-hunter
Use when you need to find code by concept (not just text). Uses Serena MCP for semantic code search across the codebase with minimal token usage. Ideal for understanding architecture, finding authentication flows, or multi-file refactoring.
What this skill does
# Semantic Code Hunter (Powered by Serena MCP)
## When to Use
- "Where do we handle X?" questions
- Finding authentication flows
- Locating validation logic
- Multi-file refactoring
- Understanding component relationships
- Finding all usages of a symbol
- Tracing dependencies
## When NOT to Use
- Small projects (< 10 files) - use Grep instead
- Simple text searches - use Grep instead
- Single-file edits - use Read instead
- You already know the exact file
## How It Works
Uses Serena MCP tools for semantic understanding:
- `find_symbol` - Find symbols by concept, not just name
- `find_referencing_symbols` - Trace code relationships
- `find_referencing_code_snippets` - Find where code is used
- `get_symbols_overview` - Understand file structure first
- Token-efficient (70% savings vs traditional search)
## Serena Tools Available
### find_symbol
Find symbols globally or locally with/containing a given name/substring.
```
Example: find_symbol("authenticate")
Finds: authenticateUser, isAuthenticated, AuthenticationService
```
### find_referencing_symbols
Find symbols that reference another symbol.
```
Example: find_referencing_symbols("User", type="function")
Finds: All functions that use the User model
```
### get_symbols_overview
Get high-level overview of symbols in a file.
```
Example: get_symbols_overview("src/services/auth.ts")
Returns: List of classes, functions, exports in file
```
### search_for_pattern
Pattern search across project (when semantic search not sufficient).
## Usage Pattern
### Step 1: Start with Overview
```
If you know the file:
1. get_symbols_overview("path/to/file.ts")
2. Identify relevant symbols
3. Use find_symbol to get details
```
### Step 2: Semantic Search
```
If you don't know the file:
1. find_symbol("concept")
2. Review results
3. Use find_referencing_symbols to trace usage
```
### Step 3: Targeted Retrieval
```
Once you know what you need:
1. Use find_symbol to get specific code
2. Only loads relevant sections (not entire files)
3. Minimal token consumption
```
## Examples
### Example 1: Find Authentication Flow
```
Task: "Where do we handle user authentication?"
Process:
1. find_symbol("auth") - Find auth-related symbols
2. Identify: authenticateUser, validateToken, etc.
3. find_referencing_symbols("authenticateUser") - Where is it called?
4. Trace the flow: Login route → Auth service → JWT generation
Result: Complete authentication flow mapped without reading full files
```
### Example 2: Multi-file Refactoring
```
Task: "Rename User model to Account"
Process:
1. find_symbol("User") - Find User model
2. find_referencing_symbols("User") - Find all usages
3. List all files that need updating
4. Use rename_symbol (Serena tool) for safe refactoring
Result: All references found and renamed consistently
```
### Example 3: Understanding Component Relationships
```
Task: "How does ProjectCard component get data?"
Process:
1. find_symbol("ProjectCard")
2. find_referencing_symbols("ProjectCard") - Where is it used?
3. Trace backwards to data source
4. Understand the data flow
Result: Complete data flow from API → Page → Component
```
## Best Practices
1. **Start broad, narrow down**
- Use find_symbol with general terms first
- Filter results by type (function, class, interface)
- Then get specific symbol details
2. **Use type filters**
- type="function" - Only functions
- type="class" - Only classes
- type="interface" - Only interfaces
3. **Leverage symbol relationships**
- find_referencing_symbols shows dependencies
- Helps understand impact of changes
- Reveals architectural patterns
4. **Combine with traditional tools**
- Serena for semantic understanding
- Grep for simple text matches
- Read for config files, documentation
## Token Efficiency
Traditional approach (without Serena):
1. Read entire files → 10,000+ tokens
2. Multiple grep iterations → 5,000+ tokens
3. Manual analysis → High cognitive load
Serena approach:
1. find_symbol → 200 tokens
2. Targeted retrieval → 500 tokens
3. Total: ~700 tokens (93% savings)
## Troubleshooting
**If Serena returns too many results:**
- Add type filter: type="function"
- Use more specific search term
- Check specific file with get_symbols_overview first
**If Serena returns no results:**
- Check spelling (case-sensitive)
- Try broader search term
- Fall back to Grep for text search
- Ensure Serena is indexed (run: serena project index)
**If symbols missing:**
- Re-index project: serena project index
- Check if file is in .gitignore
- Verify language server supports file type
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.