AxiomCode Graph plugin
A code graph built with formal methods: axiomcode impact, path and tests show an agent what an edit breaks and what to run.
- 624 ★ on the repository
- Last commit
Extended access
Why this level
- Hooks run after agent edits and write the graph into the project directory and the user cache.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add plugins/axiomcode-graphDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Hooks run after agent edits and write the graph into the project directory and the user cache.
This is third-party code. Review the repository files before installing.
What it does
AxiomCode Graph builds a code graph of a repository: for every function it knows who calls it and what it calls. Links are derived by logical rules from the receiver type rather than guessed by name. The agent queries the graph instead of searching text. The package has the `@axiomcode/code-graph` engine with the `axiomcode` command and a plugin with a skill, five MCP tools and hooks. The commands `axiomcode impact`, `axiomcode path A B` and `axiomcode tests` answer what a change reaches, how A reaches B and which tests to run after your edits.
Who it is for. Java, TypeScript and Python developers whose agent misses calls through interfaces and callbacks and skips the affected tests.
Good fit when
- Before changing a method you need to know who calls it through an interface or subclass.
- After uncommitted edits you want to run only the reachable tests.
- You need the call chain from one code point to another with code at each hop.
- The agent spends many tool calls exploring a new repository.
Not a fit when
- The project language is outside the list: Java, TypeScript and Python are stable, JavaScript and C# beta.
- You need to find files by name: the engine answers impact questions, not search.
- The FSL-1.1 license does not fit company policy.
Example request
Run `axiomcode impact` for the payment function, show the callers and list the tests that should run.Limitations
Node 22.13 or newer and Python 3 are required; on Windows also Git for Windows. On Linux arm64 native modules compile during install, so build tools are needed. The FSL-1.1-Apache-2.0 license restricts commercial use until it converts to Apache 2.0. The graph is built in the project's `.axiomcode/` and in `~/.cache/axiomcode`, and `.axiomcode/` belongs in `.gitignore`. Restart the agent session after upgrading, otherwise an old MCP server and hooks run beside the new ones.
How to disable. Run `claude plugin uninstall axiomcode@axiomcode`, then `npm uninstall -g @axiomcode/code-graph` and delete the project `.axiomcode` and `~/.cache/axiomcode`.
FAQ
How do I install it for Claude Code?
First `npm i -g @axiomcode/code-graph`, then `claude plugin marketplace add AxiomCodeAI/axiomcodegraph && claude plugin install axiomcode@axiomcode`.
Does it work with agents without plugins?
Yes, any MCP client takes an entry running `npx -y @axiomcode/code-graph mcp`. Hooks are unavailable then.
What does `axiomcode tests` do?
It lists tests reached by your uncommitted edits and ends with a `run:` line holding the command to run them.
What if the graph could not resolve a call?
Record it with `axiomcode link <file:line> <target>`. Then `impact`, `path` and `tests` follow it, labelled `[asserted]`.
Which languages are supported?
Java, TypeScript and Python are stable. JavaScript and C# are beta, and HTML and CSS are listed as beta.
Discussion
No questions or reviews yet.
Related
PluginsAn MCP server builds a local code graph so an agent can inspect calls, dependencies and the possible impact of a function change.
Structural questions about code instead of brute-forcing files: 38 languages, 42 tools, VS Code and JetBrains plugins, a CI mode
Code dependency graph for VS Code, the CLI and MCP: imports, calls, cycles, dead code and change impact.
Local code graph for agents: an MCP server returns entry points, symbol links and change impact in one call
A CLI that builds a function-level dependency graph for 34 languages and serves it to agents through a 34-tool MCP server.
CodeGraph (Rust)
codegraph-rust
A Rust code graph for agents: four MCP tools show what an edit will touch, how the architecture fits together and where the fragile spots are
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| AxiomCode Graph (this card) | no | 624 | ||
| GitNexus | no | not required | 48,470 | indexes code into a searchable knowledge graph; here links are derived from types and `impact`, `path` and `tests` answer three questions |
| graphify | no | 146,796 | builds a knowledge graph over code, docs and PDFs; this one covers code only, with precise call resolution and test selection |
README in short
The README shows Defects4J measurements, explains the typed graph, gives installs for several agents, a command table and the license terms.