code-graph

Build and maintain structural dependency graphs from codebase imports and exports.

8|Updated May 18, 2026
One-click install
npx skills add https://github.com/lalulali/vespyr --skill code-graph-lalulali
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-graph
Source: https://github.com/lalulali/vespyr/tree/main/.agents/skills/code-graph
Command: npx skills add https://github.com/lalulali/vespyr --skill code-graph-lalulali

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill keeps a codebase dependency graph current without constant background scanning, helping teams understand file relationships only when they actually need them.

Core Features & Use Cases

  • Graph initialization: Build a structural map of imports, exports, and file-level relationships across the codebase.
  • Incremental updates: Rescan only changed or deleted files to keep the graph synchronized efficiently.
  • Status inspection: Report graph freshness, size, scan counts, and regeneration timestamps for quick verification.
  • Use case: A developer changes several modules and then asks for a sync so the dependency graph reflects the new structure before architecture review.

Quick Start

Ask the assistant to initialize, refresh, or check the status of the codebase graph for the repository.

Frequently Asked Questions about code-graph

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

FAQPage Schema
How do I map code dependencies without running constant background scans?

To map code dependencies without background scanning, use an on-demand structural graph tool. It builds and maintains file-level relationships, imports, and exports only when initialization or synchronization is triggered.

What is incremental scanning for codebase dependency mapping?

Incremental scanning for codebase dependency mapping rescan only changed or deleted files. This approach efficiently synchronizes the structural graph without performing a full project rescans.

How do I check if my codebase dependency graph is fresh before an architecture review?

To check if your codebase dependency graph is fresh, run a status inspection. This reports graph freshness, size, scan counts, and regeneration timestamps to verify structural accuracy.

Can I build a structural map of imports and exports for an active software project?

Yes, you can build a structural map of imports and exports for an active software project. Graph initialization maps file-level relationships across the codebase to establish a baseline dependency structure.

What is the best way to synchronize a dependency graph after modifying several modules?

The best way to synchronize a dependency graph after modifying modules is to request an incremental update. This rescans changed files and applies a self-healing wrapper to verify graph freshness and return telemetry.