Build Knowledge Graph

Self-Evolving Skill: This skill improves through use. If a backend command drifts, a flag changes, or a new failure mode appears — fix this file (and references/backends.md) immediately, don't defer. Only update for real, reproducible issues.

Run the graphify engine on a target folder and surface what it found.

Prerequisite: graphify CLI on PATH. If missing, invoke graphify-tools:setup first.

Complement, not replacement: for symbol-level code questions (callers/callees/impact) use the codegraph MCP tools — they are sub-ms and deterministic. Reach for graphify when the corpus is mixed (code + docs + papers + images) or the question is conceptual ("what connects X to Y across these files?").

Steps

1. Scope the target

Default to the current repo, but ASK before running on anything huge — LLM extraction of docs/images costs tokens and time. Scoping heuristics: