spurpower-code-explore

Navigate repository code via call-graph edges and symbol definitions.

2|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/getspur/spur --skill spurpower-code-explore
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spurpower-code-explore
Source: https://github.com/getspur/spur/tree/main/.claude/skills/spurpower-code-explore
Command: npx skills add https://github.com/getspur/spur --skill spurpower-code-explore

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the inefficiency of relying on broad text searches like Grep or Glob for code exploration, providing a structured, graph-based approach to understanding symbol relationships, call stacks, and code impact.

Core Features & Use Cases

  • Three-Layer Retrieval Stack: Navigate code through orientation (knowledge packs), precision (symbol-level tools), and aggregation (SQL-based analysis).
  • Impact Analysis: Safely determine the blast radius of code changes by tracing call edges and identifying popular sinks.
  • Use Case: When refactoring a core function, use this skill to identify all callers across the repository, verify call-graph edges, and ensure no dependencies are silently broken.

Quick Start

Use the spurpower-code-explore skill to orient yourself on the current codebase and identify the primary entry points for the authentication module.

Frequently Asked Questions about spurpower-code-explore

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

FAQPage Schema
How do I perform code impact analysis before refactoring a function?▼

Code impact analysis traces call-graph edges and symbol definitions to identify all callers of a function across a repository, ensuring dependencies are not silently broken during refactoring.

What is graph-first code navigation and how does it differ from text search?▼

Graph-first code navigation uses a structured three-layer retrieval stack of knowledge packs, symbol-level tools, and SQL-based aggregation to provide high-fidelity context, minimizing noise from broad text searches like Grep.

How do I find all callers of a specific symbol in a repository?▼

You can find all callers by leveraging symbol resolution and call-graph edges, allowing you to precisely trace and verify dependencies across the entire codebase without broad pattern matching.

Can I use SQL-based aggregation for complex code exploration queries?▼

Yes, SQL-based aggregation serves as the third layer of the retrieval stack, enabling complex queries against symbol definitions and call-graph data for high-fidelity, context-aware code analysis.

When should I use graph analysis instead of Grep for code exploration?▼

Graph analysis is necessary when you need to understand structural relationships, trace call stacks, or determine the blast radius of changes, tasks where broad text-based search patterns produce excessive noise.