repo-graph

Plugin repo-graph from marketplace james-chahwan in James-Chahwan/repo-graph. Commands read from the repo's manifest — 9 days ago.

Skills (8)

• glia-debug

  Turn a stacktrace, failing test id or diff into the code it implicates, ranked and located, then read it. Use when a test fails, an error or traceback shows up, or you need to know where to start on a bug.

• glia-find

  Find where a feature, symbol or concept lives in a codebase, as ranked nodes with path:line, then read their source. Use for "where is X", "find the code that handles Y", "which files is this task about", or to work out which files matter before reading any.

• glia-impact

  Blast radius before changing code. Lists everything a function, route, class or whole diff reaches or is reached by, ranked and located, with likely-dead code flagged. Use before a refactor, rename, delete or signature change, for a PR review, and for "who uses this" or "what breaks if I change this

• glia-init

  Build, rebuild or wire up the glia structural map for a repository, with the history its rankings read. Use on first use in a repo, after a large refactor or branch switch, to keep the graph fresh, or to add glia (through the repo-graph MCP server) to a project's coding agents for good.

• glia-orient

  Map a codebase before opening files. Shows the services and how they talk, the entry points and where each flows, and where the glia graph is blind. Use at the start of a task in an unfamiliar or large repo, or when asked how a codebase is laid out or what's in it.

• glia-overlay

  Close glia's blind spots in a repo by writing .glia/overlay.toml stanzas: propose the gaps, write candidate stanzas from the code, measure them with glia overlay try, and accept only what the measurement keeps. Use it when glia gaps or glia coverage shows unpaired endpoints, unresolved sinks, tag-on

• glia-trace

  Follow a feature end to end across files, languages and services (frontend call, backend route, handler, data), or find the path between two named pieces of code. Use for "how does X work", "how does A reach B", or "which backend handler does this frontend call hit".

• glia

  Answer structural questions about a codebase with the glia CLI, no MCP server needed. Use it for where X is defined, what changing X (or a diff) affects, how feature Y flows across services, what calls, serves or implements X, what X writes or sends, which tests cover a change, what a change did to

MCP servers (1)

• repo-graph

  runs: uvx mcp-repo-graph

Similar plugins