search-tools

Select code search tools by query type using a decision tree.

3.9k|296|Updated Dec 23, 2025
One-click install
npx skills add https://github.com/parcadei/Continuous-Claude-v3 --skill search-tools-parcadei
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: search-tools
Source: https://github.com/parcadei/Continuous-Claude-v3/tree/main/.claude/skills/search-tools
Command: npx skills add https://github.com/parcadei/Continuous-Claude-v3 --skill search-tools-parcadei

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a structured approach to searching codebases, ensuring the most efficient and accurate tool is used based on the search objective, whether it's conceptual understanding, structural analysis, or simple text matching.

Core Features & Use Cases

  • Intelligent Tool Selection: Guides users to choose between semantic search (LEANN), structural search (AST-grep), fast text search (Morph), or literal search (Grep).
  • Optimized Search: Reduces wasted time and tokens by directing queries to the most appropriate search mechanism.
  • Use Case: When trying to understand how a specific feature like "user authentication" is implemented across a large project, this skill helps you decide whether to use LEANN for conceptual understanding or Grep for specific function names.

Quick Start

Use the search-tools skill to find all occurrences of the 'User' class definition.

Frequently Asked Questions about search-tools

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

FAQPage Schema
What is the best way to search a large codebase for conceptual features like user authentication?

The best way to search for conceptual features is using semantic search tools like LEANN, which map user needs to specific mechanisms for efficient code exploration and understanding.

How do I choose between AST-grep and Grep for code navigation?

Use a code search decision tree to choose between AST-grep for structural analysis and Grep for literal text matching, ensuring the most efficient and accurate tool is applied to your query.

When do I need structural search instead of fast text search for code exploration?

You need structural search when your objective requires analyzing code syntax and structure rather than simple text matching, optimizing search efficiency by directing queries to the appropriate mechanism.

Can I use this approach to find all occurrences of a specific class definition in a project?

Yes, you can use the search methodology to find class definitions by selecting the appropriate tool, such as fast text search via Morph or literal search via Grep, based on your query type.

Does semantic search reduce wasted time and tokens when navigating complex codebases?

Semantic search reduces wasted time and tokens by directing queries to the most appropriate search mechanism, standardizing search methodologies to efficiently map user needs to specific tools.

What are the limitations of using a single search tool for complex codebase navigation?

Using a single tool limits coverage across query types, as no single mechanism handles semantic, structural, and text-based searches simultaneously, making a standardized search strategy necessary for precision.