sym

Navigate codebases by symbol to locate callers, callees, tests, and diffs.

1|1|Updated Apr 24, 2026

Search Tags:#debugging #impact analysis #code navigation #symbol search #call graph #repository indexing #diff scoping

Ready to run

npx skills add https://github.com/luan/agents --skill sym

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sym
Source: https://github.com/luan/agents/tree/main/skills/sym
Command: npx skills add https://github.com/luan/agents --skill sym

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

sym removes the guesswork of where code lives and how it changes by letting you navigate an unfamiliar codebase around a symbol, its callers, callees, tests, and diffs.

Core Features & Use Cases

Symbol-first navigation loop: orient, locate, inspect, relate, and assess so you can reach the right files quickly.
Dependency and change context: find direct references, transitively impacted dependents, and implementations/conformances.
Evidence-oriented output: use compact agent-readable formatting for search and investigation workflows.

Quick Start

Ask: "Use sym to find what changed around the OpenStore symbol, including its callers, tests, and a symbol-scoped diff."

Frequently Asked Questions about sym

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

FAQPage Schema

How do I find where a specific symbol is defined and trace its callers in a large codebase?▼

Symbol search lets you locate where logic lives and explore its caller and callee graph. You can navigate an unfamiliar codebase by indexing the repository and querying specific symbols to find direct references and transitively impacted dependents.

What is the best way to scope a code diff to see what changed around a specific function?▼

Diff scoping by symbol allows you to see exactly what changed around a specific function or variable. By running a symbol-scoped diff, you gather precise evidence for code review or debugging without reviewing unrelated changes across the entire repository.

How do I find untested code and map test dependencies for specific symbols?▼

You can map test dependencies for specific symbols by querying test-deps and untested commands. This identifies which tests cover a symbol and highlights logic that lacks test coverage, helping you assess risk before making changes.

Can I perform impact analysis to see transitively impacted dependents before modifying a symbol?▼

Yes, impact analysis traces transitively impacted dependents before you modify a symbol. By exploring the reference and caller graph, you can assess the blast radius of a change and identify all downstream logic that relies on your target code.

Does code navigation by symbol work for finding interface implementations and schema types?▼

Code navigation by symbol supports finding interface implementations and schema types. You can query impls and types to locate conformances and structural definitions, making it easier to understand how abstract logic is realized across the repository.