codebase-navigator

Query codebase symbols, dependencies, call graphs, and git history via roam-code.

1|Updated Dec 26, 2025
One-click install
npx skills add https://github.com/DammianMiller/universal-agent-memory --skill codebase-navigator-dammianmiller
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: codebase-navigator
Source: https://github.com/DammianMiller/universal-agent-memory/tree/main/.factory/skills/codebase-navigator
Command: npx skills add https://github.com/DammianMiller/universal-agent-memory --skill codebase-navigator-dammianmiller

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill replaces slow, multi-step manual code exploration (like grep and find) with a single, powerful graph query, enabling rapid understanding of unfamiliar codebases.

Core Features & Use Cases

  • Code Comprehension: Quickly understand code structure, dependencies, and call graphs.
  • Impact Analysis: Determine the blast radius of changes and identify affected tests.
  • Use Case: Before refactoring a critical module, use roam preflight <module> to see all affected files, tests, and complexity metrics, ensuring a safe and efficient change.

Quick Start

Use the codebase-navigator skill to get a full codebase briefing.

Frequently Asked Questions about codebase-navigator

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

FAQPage Schema
How do I analyze codebase dependencies and call graphs without using grep and find?▼

You can analyze codebase dependencies and call graphs by executing semantic graph queries to retrieve symbols, complexity metrics, and git history, replacing manual multi-step grep and find exploration with a single query.

What is the best way to determine the blast radius of a multi-file refactor?▼

Determining the blast radius of a multi-file refactor is best done by running a preflight graph query to identify all affected files, tests, and complexity metrics, ensuring you understand the full impact before making changes.

Can I get a codebase overview for unfamiliar code before starting an editing session?▼

Yes, you can get a codebase overview for unfamiliar code by running a semantic graph query that provides immediate context on structure, dependencies, and call graphs for initial session briefings.

Does semantic graph navigation work for understanding git history and symbol relationships?▼

Semantic graph navigation works for understanding git history and symbol relationships by querying the codebase graph to return context on symbols, dependencies, call graphs, and historical changes in a single request.

How do I identify affected tests when modifying a critical module?▼

To identify affected tests when modifying a critical module, you run a preflight graph query that maps the module's call graph and dependencies to surface all connected test files and complexity metrics.