Agent skill · software engineering · aiskillstore
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.
Why this skill is useful
Adds executable commands for semantic code search that enhance understanding of code architecture and relationships.
What it needs
Requires serena installed locally. About 3k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
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: findsymbol - Find symbols by concept, not just name findreferencingsymbols - Trace code relationships findreferencingcodesnippets - Find where code is used getsymbolsoverview - Understand file structure first Token-efficient (70% savings vs traditional search) Serena Tools Available findsymbol Find symbols globally or locally with/containing a given name/substring. findreferencingsymbols Find symbols that reference another symbol. getsymbolsoverview Get high-level overview of symbols in a file. searchforpattern Pattern search across project (when semantic search not sufficient). Usage Pattern Step 1: Start with Overview Step 2: Semantic Search Step 3: Targeted Retrieval Examples Example 1: Find Authentication Flow Example 2: Multi-file Refactoring Example 3: Understanding Component Relationships Best Practices 1. Start broad, narrow down Use findsymbol 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 findreferencingsymbols 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. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/semantic-code-hunter