search-tools — Claude Code skill: what it does, how to install
search-tools is a Claude Code skill that routes code searches to LEANN, AST-grep, Morph, or Grep based on the task.
MIT ★ 3,951 updated 2026-01-26
npx skills add parcadei/Continuous-Claude-v3 --skill search-tools -a claude-codeWhat search-tools does
The skill defines a search routing hierarchy for Claude Code. Instead of running basic regex queries across the entire repository, the agent routes conceptual questions to LEANN, structural syntax patterns to AST-grep, and text lookups to Morph or Grep.
Each search backend has prerequisites outlined in the rule. LEANN requires an index built with leann build, AST-grep depends on an MCP server, and Morph needs an API key. Because user-invocable is set to false, Claude Code applies these routing rules automatically during code exploration.
What it helps with
- Route codebase queries to the right search backend
- Inspect architectural concepts using semantic search in LEANN
- Find syntax structures and function calls using AST-grep
- Accelerate codebase text lookups with Morph
Example prompts for the agent
- How does authentication work in this codebase and where is rate limiting handled?
- Find all React components using useState and locate calls to foo()
- Search for files mentioning TODO comments and inspect class ProviderAdapter
How to install search-tools
1Skills CLI (Vercel)
npx skills add parcadei/Continuous-Claude-v3 --skill search-tools -a claude-code2Manually: put the files in place
~/.claude/skills/search-tools/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/search-tools/
1Skills CLI (Vercel)
npx skills add parcadei/Continuous-Claude-v3 --skill search-tools -a codex2Manually: put the files in place
.agents/skills/search-tools/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add parcadei/Continuous-Claude-v3 --skill search-tools -a cursor2Manually: put the files in place
.cursor/skills/search-tools/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install parcadei/Continuous-Claude-v3 .claude/skills/search-tools2Manually: put the files in place
.github/skills/search-tools/SKILL.md1Skills CLI (Vercel)
npx skills add parcadei/Continuous-Claude-v3 --skill search-tools -a gemini-cli2Platform CLI
gemini skills install https://github.com/parcadei/Continuous-Claude-v3 --path .claude/skills/search-toolsManually: put the files in place
.devin/skills/search-tools/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about search-tools
How to install search-tools in Claude Code?
Run npx skills add parcadei/Continuous-Claude-v3 --skill search-tools -a claude-code in your terminal.
What does search-tools do?
It provides a decision tree that directs Claude Code to semantic, structural, or literal code search tools depending on the query.
What is required to use all tools in the search hierarchy?
LEANN requires an index created with leann build, AST-grep requires an MCP server, and Morph requires an API key.
Source text
SKILL.md · MIT
--- name: search-tools description: Search Tool Hierarchy user-invocable: false --- # Search Tool Hierarchy When searching code, use this decision tree: ## Decision Tree ``` Need CONCEPTUAL/SEMANTIC search? (how does X work, find patterns, understand architecture) → Use LEANN (/leann-search) - embedding-based semantic search → PreToolUse hook auto-redirects semantic Grep queries Need to understand code STRUCTURE? (find function calls, class usages, refactor patterns) → Use AST-grep (/ast-grep-find) Need to find TEXT in code? → Use Morph (/morph-search) - 20x faster → If no Morph API key: fall back to Grep tool Simple one-off search? → Use built-in Grep tool directly ``` ## Tool Comparison | Tool | Best For | Requires | |------|----------|----------| | **LEANN** | Semantic search: "how does caching work", "error handling patterns", conceptual queries | Index built | | **AST-grep** | Structural patterns: "find all calls to `foo()`", refactoring, find usages by type | MCP server | | **Morph** | Fast text search: "find files mentioning error", grep across codebase | API key | | **Grep** | Literal patterns, class/function names, regex | Nothing (built-in) | ## Examples **LEANN** (semantic/conceptual): - "how does authentication work" - "find error handling patterns" - "where is rate limiting implemented" **AST-grep** (structural): - "Find all functions that return a Promise" - "Find all React components using useState" - "Refactor all imports of X to Y" **Morph** (text search): - "Find all files mentioning 'authentication'" - "Search for TODO comments" **Grep** (literal): - `class ProviderAdapter` - `def __init__` - Regex patterns ## LEANN Commands ```bash # Search with semantic query leann search opc-dev "how does blackboard communication work" --top-k 5 # List available indexes leann list # Rebuild index (when code changes) leann build opc-dev --docs dir1 dir2 --no-recompute --no-compact --force ```
© parcadei · MIT · parcadei/Continuous-Claude-v3