code-navigation

Builds local structural indexes to find definitions, trace callers, and map repository code.

Updated Sep 6, 2026
One-click install
npx skills add https://github.com/oxie/prime-agent-skills --skill code-navigation-oxie
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-navigation
Source: https://github.com/oxie/prime-agent-skills/tree/main/code-navigation
Command: npx skills add https://github.com/oxie/prime-agent-skills --skill code-navigation-oxie

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Navigating a large codebase with plain grep and file reads becomes slow and error-prone when you need cross-file orientation, caller tracing, or change-impact analysis. This Skill builds a local structural index of a Git repository so you can locate definitions, inspect file APIs, and trace dependencies without running any target-project code. ## Core Features & Use Cases - Structural indexing and mapping: Index a repository and get a capped map of directories, hubs, and hotspots derived from a tree-sitter based code graph. - Definition and symbol lookup: Find symbols by exact name or lexical query, and view a file's outline with precise line spans. - Caller and dependency tracing: Trace inbound or outbound edges around a symbol with configurable depth, including edge confidence and endpoint locations. - Use Case: Before renaming a shared validateToken function, trace its inbound callers at depth 2, inspect each caller's contract in the original source, then make the change and run the project's own tests. ## Quick Start Ask the agent to index the current repository and trace the callers of a specific function using the code-navigation skill.

Frequently Asked Questions about code-navigation

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

FAQPage Schema
How do I find all callers of a function in a large repository?▼

Run the trace command with --symbol set to the function name, --direction in, and a depth between 1 and 5. The result lists caller nodes with their file paths, line spans, and edge relations; disambiguate duplicate names with an exact ID or --file.

How do I get an outline of a source file's symbols?▼

Use the outline command with --file set to the exact repository-relative path of an indexed source file. It returns the file's definitions with names, kinds, and line spans, capped by the configurable result limit.

What languages does tree-sitter code indexing support?▼

The runtime bundles grammars for TypeScript/TSX, JavaScript, Python, Go, Java, Kotlin, PHP, R, and Swift, plus generic and container formats. Validation focuses on TypeScript and Python; other languages may produce symbols without precise dependency edges.

Does the code index replace grep and reading source files?▼

No. The graph can miss dynamic calls, package aliases, and re-exports, and it excludes dot paths, ignored files, and files over 1 MB. Keep ordinary search for configuration, docs, and templates, and always open the decisive original source before editing.

Why does a code navigation query report unavailable or stale health?▼

The launcher fails closed when the pinned runtime manifest, patch hash, cache ownership, or source hashes do not verify, or when time and output bounds are exceeded. In that state use ordinary source search instead of trusting an old graph.

Can the indexer run target project code or access the network?▼

No. No target-repository code is executed, and the launcher applies inherited seccomp rules denying network syscalls plus no_new_privs. It also disables Git hooks and global configuration, though this is not a full filesystem sandbox.