deepsearch

Automate multi-pass codebase searches to map symbols, dependencies, and data flows.

31|3|Updated Dec 12, 2025
One-click install
npx skills add https://github.com/JeremyDev87/codingbuddy --skill deepsearch-jeremydev87
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deepsearch
Source: https://github.com/JeremyDev87/codingbuddy/tree/main/packages/rules/.ai-rules/skills/deepsearch
Command: npx skills add https://github.com/JeremyDev87/codingbuddy --skill deepsearch-jeremydev87

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Broad, multi-pass searches uncover hidden connections across a codebase, enabling thorough understanding beyond simple grep.

Core Features & Use Cases

  • Multi-pass search strategy: combines varied search strategies to map code relationships.
  • Symbol mapping & dependency tracing: builds a map of definitions, references, and data/control flows.
  • Use Case: When refactoring a feature across modules, analyze touched components and dependencies to prevent regressions.

Quick Start

Run a multi-pass search across the repository to identify all files and symbols related to a target feature.

Frequently Asked Questions about deepsearch

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

FAQPage Schema
How do I trace data flow and dependencies across a large codebase?

Multi-pass search strategies automate tracing data flow and dependencies across a large codebase by combining varied search methods to build a map of definitions, references, and control flows. This process surfaces hidden connections beyond simple grep.

What is multi-pass codebase discovery and when do I need it?

Multi-pass codebase discovery is a technique that applies varied search strategies to map code relationships and surface all relevant files and symbols. You need it for understanding end-to-end feature behavior or auditing dependencies in large repositories.

How do I analyze touched components before refactoring a feature across modules?

To analyze touched components before refactoring a feature across modules, run a broad multi-pass search to map code relationships and trace dependencies. This builds a comprehensive symbol map to prevent regressions during the refactoring process.

Does multi-pass static analysis work better than grep for understanding end-to-end feature behavior?

Multi-pass static analysis works better than grep for understanding end-to-end feature behavior because it combines varied search strategies to map definitions, references, and data flows. Grep alone misses hidden connections across large repositories.

Can I use multi-pass search for cross-reference validation in large repositories?

Yes, you can use multi-pass search for cross-reference validation in large repositories. It automates broad searches to surface all relevant files and symbols, satisfying requirements for multi-strategy discovery and cross-reference validation.