Coregraph

Use the `coregraph` CLI/MCP — a code symbol graph (tree-sitter + stack-graphs) — as the PRIMARY tool for structural and relational code questions, in preference to a raw grep/read sweep. Trigger when the user asks to find callers / who uses a symbol / where a symbol is defined / what it calls or depends on / how it is wired up, analyze change impact or blast radius, find dead code / orphans / unused symbols, detect cross-file inconsistencies (enum / api-path / config-key / doc drift), see the impact of a git diff, get a structural symbol-graph overview (symbol counts, top files, edge breakdown via `stats`), or explicitly invokes coregraph — e.g. "who calls X", "where is X defined", "what does X depend on", "what breaks if I change X", "impact 분석", "dead code 찾아줘", "누가 이거 호출해", "orphan 찾아줘", "cross-file 불일치 검사", "coregraph로 분석", "symbol graph 뽑아줘", "코드 그래프로 보여줘". Do NOT trigger for reading the logic inside a single function, for non-symbol content (comments, string contents, config values, prose, TODO hunting), or for a general narrative "what does this project do / explain this repo" overview — read the README or source for those.

mkdir -p ~/.claude/skills/coregraph
curl -L https://claudskills.com/skills/coregraph/SKILL.md \
  -o ~/.claude/skills/coregraph/SKILL.md

@misc{coregraph-2026,
  author    = {simplecore-inc},
  title     = {Coregraph [Claude Code skill]},
  year      = {2026},
  publisher = {ClaudSkills},
  url       = {https://claudskills.com/skills/coregraph/}
}