eq-code-graph

Answers structural codebase questions using a pre-indexed tree-sitter code knowledge graph.

Updated Aug 3, 2026
One-click install
npx skills add https://github.com/everquint/frontend-skills --skill eq-code-graph-everquint
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: eq-code-graph
Source: https://github.com/everquint/frontend-skills/tree/main/skills/productivity/eq-code-graph
Command: npx skills add https://github.com/everquint/frontend-skills --skill eq-code-graph-everquint

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @colbymchenry/codegraph.

What problem does it solve? Answering structural questions about a codebase — what depends on a symbol, what the blast radius of a change is, how a feature flows end-to-end — normally requires slow, error-prone grep-and-read loops. This Skill uses a pre-indexed code knowledge graph to answer those relationship questions in one tool call. ## Core Features & Use Cases - Impact analysis: Run codegraph impact "symbol" to get the transitive dependency closure of a symbol before changing it. - Flow tracing: Use codegraph explore to trace how a feature like authentication works end-to-end, with call paths and source in one shot. - Caller/callee lookup: Query codegraph callers and codegraph callees to map symbol relationships, exposed to the agent over MCP. - Use Case: Before renaming a shared utility, ask what depends on it — the graph returns the blast radius roughly 5x faster than grep-and-read, then confirm completeness with ripgrep. ## Quick Start Ask the agent what depends on a specific function or component in this repo and have it answer using the codegraph index, confirming completeness with ripgrep.

Frequently Asked Questions about eq-code-graph

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

FAQPage Schema
How do I find the blast radius of changing a function?

Run codegraph impact with the symbol name to get its transitive dependency closure in one call. Confirm completeness afterward with ripgrep, since the graph under-counts arrow-function components.

When should I use a code knowledge graph instead of ripgrep?

Use the graph for relationship questions like impact, callers, callees, and flow tracing. Use ripgrep for exhaustive enumeration such as finding every call site or string occurrence, where grep is faster and complete.

What are the limitations of codegraph callers and impact analysis?

The graph misses arrow-function React components in callers and impact results, and it cannot see literal shape-coupling such as test mocks hardcoding an object shape. Treat counts as a starting map, not a complete answer.

How do I install codegraph safely for one project?

Install the npm package, disable telemetry, run codegraph init in the project, add .codegraph/ to .git/info/exclude, and register the MCP server with --scope local. Avoid the global install command, which rewrites every agent's MCP config.

Is codegraph required by the frontend standard?

No. It is an optional recommendation documented in ADR 0020; no gate, hook, or review step checks for it, and a repo without it is fully conformant with the standard.