Skip to main content
Back to Blog
β€’Rafael Gonzalez

The Claude Code graph stack: Graphify and Repomix

Claude Code runs the long job. Graphify answers what depends on what. Repomix packs the tree when the graph is the wrong shape. How the three actually hand off.

Use this stack as a page: the Claude Code graph stack.

Claude Code is the agent you send away for the long job: tests, git, a refactor that should not need you at the keyboard. It still needs a shape of the repo. A 400k-token paste of src/ is not a shape. Neither is β€œjust grep it.”

The stack that stuck is three tools with three jobs:

  1. Claude Code β€” the host that runs while you step away.
  2. Graphify β€” the graph you query for blast radius.
  3. Repomix β€” the packer when you actually need the files, not the edges.

Why the long job still greps

Claude Code can run commands. That is the point. Left alone, it will find and rg until the context window is a junk drawer: lockfiles, generated clients, the one file that mattered sitting under a match on TODO.

Graphify is the question β€œwhat calls this?” Repomix is the question β€œgive me the tree as one file the model can read.” They are not substitutes.

  • Use Graphify when the job is navigation and blast radius.
  • Use Repomix when the job is the text of the files, with ignore rules, after you already know which subtree.

GitIngest is the sibling when the repo is still on GitHub and you have not cloned it. That is a different stack: Codex ingest. See also Repomix vs GitIngest.

The three roles

Claude Code owns the outer loop

Hand it the branch, the failing test, and the constraint. Do not paste the whole monorepo into the first message. Do not ask it to be a diagramming tool.

Graphify owns the edges

Index, then ask. β€œWhat imports billing/invoice.ts?” is a Graphify question. β€œRewrite invoice.ts” is a Claude Code question. Mixing them is how you get a confident edit that never saw the worker.

Repomix owns the pack

npx -y repomix when the agent needs the files Graphify will not stringify for you. Respect ignore files. Do not pack node_modules. Do not treat the XML dump as a license to skip the graph query.

One job, four steps

  1. Open the repo in Claude Code. Stay on one branch.
  2. Index with Graphify and ask what calls the module you are about to change.
  3. If the agent still lacks the file, pack with Repomix and paste that.
  4. Let Claude Code run the tests. Keep Graphify as the map, not as the editor.

Install and hosts: Claude Code, Graphify, Repomix, and the Claude Code add-ons hub.