graphify

Builds a local code dependency graph to answer impact and usage questions about JavaScript and TypeScript symbols.

Updated May 26, 2026
One-click install
npx skills add https://github.com/avel123111/triplanio --skill graphify-avel123111
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: graphify
Source: https://github.com/avel123111/triplanio/tree/main/.claude/skills/graphify
Command: npx skills add https://github.com/avel123111/triplanio --skill graphify-avel123111

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires graphifyy.

What problem does it solve? When modifying unfamiliar code, it is hard to know what will break if you change a function, who already uses a component, or which files are architectural hubs. This Skill builds a local import and call graph of the repository so those questions get concrete answers with file paths and line numbers. ## Core Features & Use Cases - Blast radius analysis: Run graphify affected "useProStatus" to list every file and line impacted by a change to a symbol. - Symbol relationship inspection: Run graphify explain "Btn" to see who calls a symbol and what it calls. - Architecture mapping: Run graphify god-nodes --top 12 to identify the load-bearing nodes of the project. - Use Case: Before creating a new component, check the reuse gate by running affected and explain on existing candidates to see what already exists and who consumes it. ## Quick Start Ask the assistant to build the code graph with graphify and show what would be affected if you modified a specific function or component.

Frequently Asked Questions about graphify

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

FAQPage Schema
How do I find what breaks if I change a function in my codebase?

Run graphify affected with the symbol name to get a blast radius list with file paths and line numbers. If the result is empty, run graphify explain with the same name to check for ambiguous symbol matches before concluding nothing uses it.

How to build a code dependency graph for a JavaScript project?

Install the CLI with uv tool install graphifyy, add ~/.local/bin to PATH, then run graphify extract . --code-only. The graph is written to graphify-out/graph.json in about eight seconds and should never be committed.

Can a static code graph prove that code is dead?

No. The graph only sees static JS/TS references, so JSX usage, string-invoked edge functions, CSS classes, i18n keys, and RPC calls appear as having no incoming links. Dead code must be confirmed manually across source, edge functions, migrations, locales, and stylesheets.

Why does graphify affected return an empty list for a used component?

Empty output usually means the symbol name is ambiguous, matching multiple nodes in the graph. Run graphify explain with the same name to see the ambiguity, then repeat affected with the full node id.

Does the code graph index database schema and SQL functions?

Only with the optional graphifyy[sql] install, which adds tables, functions, and triggers as nodes. These database nodes remain disconnected from TypeScript code and slow the build roughly sixfold, so install it only when mapping the schema.