codebase-understanding

Analyze codebase structure, call flows, and change impact using the GitNexus knowledge graph.

3|Updated Jun 29, 2026
One-click install
npx skills add https://github.com/ruskicoder/system-prompts --skill codebase-understanding-ruskicoder
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: codebase-understanding
Source: https://github.com/ruskicoder/system-prompts/tree/main/prompt-orchestrator/.opencode/skills/codebase-understanding
Command: npx skills add https://github.com/ruskicoder/system-prompts --skill codebase-understanding-ruskicoder

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gitnexus.

What problem does it solve? Navigating unfamiliar codebases and predicting the blast radius of code changes is slow and error-prone when done by manually reading files. This Skill uses the GitNexus knowledge graph to answer questions about symbol dependencies, execution flows, and change impact directly. ## Core Features & Use Cases - Execution Flow Tracing: Query call chains between symbols, inspect callers and callees, and read step-by-step process traces to understand how code behaves. - Impact Analysis: Compute the blast radius of a change with depth-limited upstream and downstream analysis, and map git diffs to affected execution flows before committing. - Guided Workflows: Follow structured procedures for exploring new code, debugging bugs, planning safe edits, and verifying changes, including risk-level assessment and raw Cypher graph queries. - Use Case: Before renaming a shared validation function, run an impact query to list every direct caller, check which execution processes depend on it, then perform a coordinated multi-file rename. ## Quick Start Ask the AI to trace how the login flow reaches the database layer and show the impact of changing the authenticate function.

Frequently Asked Questions about codebase-understanding

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

FAQPage Schema
How do I trace a call flow between two functions?▼

Use the trace tool with from and to symbol names to get the shortest call chain between them. You can also read the gitnexus process resource for a step-by-step execution trace of a specific flow.

How to analyze the impact of changing a function before editing?▼

Run the impact tool with the target symbol, direction upstream, and maxDepth around 3. Depth 1 callers will break directly, depth 2 are likely affected, and depth 3 may need testing.

What is GitNexus and how do I set it up?▼

GitNexus is a code knowledge graph tool that indexes your repository for symbol and flow queries. Run npx gitnexus analyze to build the index, optionally with --embeddings for semantic search, and check freshness with node .gitnexus/run.cjs status.

Can I run custom graph queries against my codebase?▼

Yes, the cypher tool accepts raw Cypher statements against the indexed graph. You can match callers of a function, list functions in a file, or find processes a symbol participates in.

Why does the codebase query return stale or missing results?▼

The GitNexus index is likely outdated or was never built. Run npx gitnexus analyze --force to re-index the repository, then verify status with node .gitnexus/run.cjs status.