skills.rest
getspur
getspurOFFICIAL
Explore all skills by this author →
WebsiteGitHub

code-explore

Provides graph-based navigation and analysis of codebases for structured querying and impact assessment.

2|Updated Apr 15, 2026
Search Tags:#refactoring#mcp#static-analysis#impact-analysis#code-navigation#graph-analysis
One-click install
npx skills add https://github.com/getspur/spur --skill code-explore-getspur
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-explore
Source: https://github.com/getspur/spur/tree/main/.spur/skills/code-explore
Command: npx skills add https://github.com/getspur/spur --skill code-explore-getspur

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the inefficiency and inaccuracy of using grep, glob, or manual file-walking for code navigation by providing a structured, graph-based retrieval stack that understands symbol relationships, call edges, and dependency contexts.

Core Features & Use Cases

  • Three-Layer Retrieval: Navigate code using orientation (knowledge packs), precision (symbol-specific tools), and aggregation (SQL-based analysis).
  • Impact Analysis: Safely determine the blast radius of refactors or renames by querying resolved call edges and unresolved labels.
  • External Package Support: Seamlessly explore dependency source code and upstream packages with dedicated indexing and search tools.

Quick Start

Use the code-explore skill to identify all callers of the function handle_submit_plan and assess the impact of a potential refactor.

Frequently Asked Questions about code-explore

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

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

Impact analysis for refactoring requires querying resolved call edges and unresolved labels to determine the blast radius. You trace all callers of a specific function to accurately assess the structural impact of renames or modifications.

What is the best way to navigate codebases instead of using grep?▼

Graph-based code navigation replaces inefficient text-based search methods like grep by understanding symbol relationships and call edges. It provides structured retrieval through orientation packs, precision symbol lookup, and SQL-based aggregation.

Can I trace call graphs across external dependencies and upstream packages?▼

Yes, you can trace call graphs across external dependencies. Dedicated indexing and search tools allow you to seamlessly explore dependency source code and upstream packages alongside your local worktrees.

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

Finding all callers of a symbol requires precision retrieval tools that query resolved call edges within a code graph. This method replaces manual file-walking by directly returning exact symbol locations and their invocation contexts.

When should I use static analysis over text search for code exploration?▼

You should use static analysis over text search when you need to understand dependency contexts and symbol relationships. Graph queries provide deterministic results for code exploration, ensuring refactoring safety where text search returns inaccurate matches.

Related Skills

Explore More Software Engineering Skills→
phnx-labsphnx-labs
15

cgraph

Map symbols, call hierarchies, and dependency relationships in codebases.

Official
Advanced
lciaccilciacci

code-graph

Query indexed code graphs to trace symbols, dependencies, and callers.

Community
Advanced
philo-grovesphilo-groves
12

maxtac-sast-control-flow-graph

Construct static analysis graphs for reachability, guard dominance, and path feasibility.

Community
Advanced
ollieb89ollieb89

smart-explore

Search code symbols and retrieve implementations using tree-sitter AST parsing.

Community
Intermediate