symdex-code-search

Search repository symbols, callers, callees, and HTTP routes via SymDex endpoints.

205|22|Updated Mar 8, 2026
One-click install
npx skills add https://github.com/husnainpk/SymDex --skill symdex-code-search
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: symdex-code-search
Source: https://github.com/husnainpk/SymDex/tree/main/skills/symdex-code-search
Command: npx skills add https://github.com/husnainpk/SymDex --skill symdex-code-search

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

SymDex-code-search eliminates token-heavy, broad file browsing by returning precise symbol slices, file outlines, route handlers, and call graph traces so agents and developers can find definitions and usages quickly and efficiently.

Core Features & Use Cases

  • Symbol and slice retrieval: locate function, class, or method definitions and return the exact code needed.
  • Semantic and text search: find code by intent or literal text to surface relevant implementations without scanning entire files.
  • Call graph and route tracing: trace who calls a symbol, what a symbol calls, and locate HTTP routes for fast debugging or feature work.
  • Index management: check index freshness, create workspace or global indexes, and prefer lightweight structural refreshes or embedding-backed semantic search when needed.
  • Use case: find the HTTP route for /api/checkout, retrieve the handler implementation, and list callers to assess impact before editing.

Quick Start

Use the symdex-code-search skill to locate a symbol definition, show its callers, and return a concise code slice from the current repository.

Frequently Asked Questions about symdex-code-search

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

FAQPage Schema
How do I find symbol definitions and trace callers in a local repository without reading entire files?

Code search and navigation retrieves precise symbol slices and call graph traces from an indexed local repository. It locates function, class, or method definitions and returns exact code segments without token-heavy file browsing.

Can I trace HTTP routes and find their handler implementations during feature development?

Yes, HTTP route tracing locates specific endpoints like /api/checkout and retrieves their handler implementations. It also lists callers to help assess impact before editing, streamlining feature development and debugging workflows.

What's the best way to search for code by intent rather than literal text matches?

Semantic code search finds implementations by intent rather than literal text. It requires an optional semantic embedding backend to surface relevant code without scanning entire files, complementing standard text-based symbol searches.

How do I generate file outlines and check index freshness for a repository?

File outline generation and index status checks are supported through dedicated tool endpoints. You can verify index freshness, create workspace or global indexes, and perform lightweight structural refreshes to maintain accurate code navigation.

Does semantic search require a specific backend or can it work with a standard repository index?

Semantic search requires an optional semantic embedding backend to function. A standard indexed SymDex state, either global or workspace-local, handles structural symbol retrieval, while the embedding backend is only needed for intent-based queries.

Why use code navigation tools instead of manually browsing files during code review?

Code navigation eliminates token-heavy file browsing by returning precise symbol slices, call graphs, and file outlines. It allows you to quickly find definitions, trace usages, and locate routes during code review, debugging, and feature development.