skills.rest
drhalto
drhaltoCOMMUNITY
Explore all skills by this author →
GitHub

mako-graph

Trace dependency paths and estimate change impact across project files.

51|5|Updated Apr 26, 2026
Search Tags:#impact analysis#dependency graph#symbol tracing#code relationships#change planning#import cycles
One-click install
npx skills add https://github.com/drhalto/agentmako --skill mako-graph
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mako-graph
Source: https://github.com/drhalto/agentmako/tree/main/mako-ai-claude-plugin/skills/mako-graph
Command: npx skills add https://github.com/drhalto/agentmako --skill mako-graph

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you understand how code elements relate to each other so you can answer impact questions, trace dependencies, and plan safe changes without guessing.

Core Features & Use Cases

  • Relationship Discovery: Inspect neighbors, paths, and higher-level flows across files, symbols, routes, tables, and RPCs.
  • Impact Analysis: Estimate the blast radius of a proposed change with import dependency and downstream analysis.
  • Symbol Inspection: Identify important declared and exported symbols in a file before editing it.
  • Use Case: A developer wants to rename a shared module and needs to know which components, flows, and imports will be affected before making the change.

Quick Start

Ask the skill to trace the dependency path between two project nodes and estimate the impact of changing the source file.

Frequently Asked Questions about mako-graph

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

FAQPage Schema
How do I estimate the blast radius of a code change before modifying a shared module?▼

To estimate the blast radius of a code change, you analyze import dependencies and downstream relationships to identify affected components and flows. This impact analysis reveals exactly which files and symbols will be impacted by editing a shared module.

What is the best way to trace the dependency path between two project files?▼

Tracing the dependency path between two project files involves inspecting neighbors and mapping the import graph to connect the source and target nodes. This path tracing provides evidence-backed visibility into the exact file-to-file relationship.

Can I use impact analysis to identify exported symbols in a file before editing?▼

Yes, impact analysis includes symbol inspection to identify important declared and exported symbols within a target file. This allows you to understand the file's interface and downstream usage before making any modifications.

Do I need a fully indexed project to map end-to-end flows and code relationships?▼

Yes, mapping end-to-end flows and code relationships requires a fully indexed project to access the necessary graph, import, and symbol inspection tools. This indexed environment provides the structural data needed to produce evidence-backed tracing results.

Why does planning a multi-file change require analyzing code relationships first?▼

Planning a multi-file change requires analyzing code relationships first to understand how dependencies, imports, and symbols intersect across the project. This relationship discovery prevents unexpected breakage by mapping the full downstream impact before implementation.

Related Skills

Explore More Software Engineering Skills→
murphytruemanmurphytrueman
155

codebase-index

Generate a machine-readable index of design system components and dependencies.

Community
Advanced
jimmymalhanjimmymalhan
1

Blast Radius

Analyze file dependencies and test coverage to identify affected files and relevant test suites.

Community
Intermediate
kriscendobotkriscendobot
3

coverage-driven-testing

Increase test coverage and identify unreachable code in a monorepo.

Community
Advanced
backengineeringbackengineering
434

dynamic-instrumentation

Instrument binaries and trace runtime behavior using LLVM infrastructure.

Official
Advanced