deepsearch

Search codebases for concept implementations and trace import trails to cited locations.

Updated Feb 20, 2026
One-click install
npx skills add https://github.com/ssccio/cc-on-web-base --skill deepsearch-ssccio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deepsearch
Source: https://github.com/ssccio/cc-on-web-base/tree/main/skills/deepsearch
Command: npx skills add https://github.com/ssccio/cc-on-web-base --skill deepsearch-ssccio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of not knowing where a concept, feature, or implementation lives inside a large, unfamiliar codebase.

Core Features & Use Cases

  • Broad Search: Finds exact matches and related term variations across common locations like components, utils, services, and hooks.
  • Deep Dive: Opens matching files and traces imports/exports to understand connections and upstream/downstream usage.
  • Synthesis: Produces a concise map of primary locations, related dependencies/consumers, usage patterns, and key insights with file paths and line numbers.

Quick Start

Use the deepsearch skill to find how the application implements a specific feature by searching for the concept and tracing all related imports and usages with cited file paths and line numbers.

Frequently Asked Questions about deepsearch

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

FAQPage Schema
How do I locate where a specific feature is implemented inside an unfamiliar codebase?

To locate a feature implementation inside an unfamiliar codebase, perform a broad search for exact matches and related terms across common locations like components and utils, then trace imports to map primary locations with file paths and line numbers.

What is the best way to trace import and export trails for codebase architecture mapping?

Tracing import and export trails for architecture mapping involves opening matching files to follow upstream and downstream usages, synthesizing connections into a concise map of related dependencies, consumers, and key insights with cited file paths.

How can I find usage patterns of a concept to assist with refactoring discovery?

Finding usage patterns for refactoring discovery requires searching for the specified concept across services and hooks, opening matching files, and synthesizing primary locations with related downstream consumers and precise file paths and line numbers.

Does codebase search work when I have a query but do not know the relevant file names?

Codebase search works effectively when you have a query but lack relevant file names by executing broad and deep searches across common code locations to find exact matches and related term variations.

How do I search across common code locations like utils and hooks during debugging?

Searching across common code locations like utils and hooks during debugging requires finding exact matches and related term variations, then opening files to trace imports and map architecture with file paths and line numbers.