deepsearch

Search codebases for queries and return matches with file paths and line numbers.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/lpjhelder/kronon-forge --skill deepsearch-lpjhelder
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deepsearch
Source: https://github.com/lpjhelder/kronon-forge/tree/main/skills/deepsearch
Command: npx skills add https://github.com/lpjhelder/kronon-forge --skill deepsearch-lpjhelder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Developers often need to locate where a particular function, class, or concept is implemented or used across a large codebase, which can be time‑consuming and error‑prone.

Core Features & Use Cases

  • Broad Search: Finds exact matches, related terms, and scans common directories (components, utils, services, hooks).
  • Deep Dive: Reads matching files, follows import/export relationships, and maps usage trails.
  • Synthesis: Summarizes primary implementations, related files, usage patterns, and key insights with file paths and line numbers.
  • Use Case: Quickly identify all implementations of an authentication module before refactoring.

Quick Start

Ask deepsearch to locate every implementation of the authentication module in the project.

Frequently Asked Questions about deepsearch

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

FAQPage Schema
How do I search a codebase for all implementations of a specific function or module?

Searching a codebase involves scanning directories like components, utils, services, and hooks for exact matches and related terms. The tool reads matching files, follows import relationships, and returns primary locations with file paths and line numbers.

What is source code pattern matching and how does it map usage trails across a repository?

Source code pattern matching locates exact matches and related terms across a repository. It reads matching files, follows import and export relationships, and synthesizes primary implementations, usage patterns, and key insights with file paths and line numbers.

How do I locate every usage of a pattern across components, utils, services, and hooks before refactoring?

To locate every usage before refactoring, perform a broad search across components, utils, services, and hooks. The tool reads matching files, follows imports, and maps usage trails with file paths and line numbers to guide your refactoring.

Can I find related files and import relationships when searching for a code pattern in my repo?

Yes, you can find related files and import relationships during a repo search. The deep dive feature reads matching files, follows import and export relationships, and maps the complete usage trail across the codebase.

Does deep code search work for analyzing large projects with complex directory structures?

Deep code search works for large projects by scanning common directories such as components, utils, services, and hooks. It locates exact matches, reads matching files, follows import relationships, and synthesizes key insights with file paths and line numbers.

What is the best way to locate authentication module implementations across a repository?

The best way to locate authentication module implementations is to query the specific concept. The search scans directories like components and services, reads matching files, follows imports, and returns primary locations with file paths and line numbers.