DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to trace the exact call path between two functions with Axiomcodegraph

Show every hop from a caller to a target function, with source lines, before you change code.

Who it is forA developer who has to change a function and needs to know how a caller reaches it, especially through interfaces or other files.

The problemGrep cannot see calls made through an interface, a subclass or a callback, so a search can miss the real route through the code.

The outcomeA numbered list of places along the call chain, each with the surrounding code and the line that matters, so you can see the full route before editing.

What you need first

  • Node.js 22.13 or newer
  • Python 3 (python3, or python or py on Windows)
  • Git for Windows on Windows, since the CLI runs under its bash
  • A supported AI agent or any MCP client, if you want agent use

Steps

  1. Install the engine with npm i -g @axiomcode/code-graph.
  2. Confirm the install with axiomcode --version.
  3. In your project folder, run axiomcode path main Ledger.put with your own caller and target names.
  4. Read each numbered hop and its source line, checking that the chain matches the code you plan to change.
  5. Add .axiomcode/ to your .gitignore so the graph folder stays out of version control.

Prompt for your agent

In the <repo> project, run `axiomcode path <caller> <target>` to list the call chain from <caller> to <target>. Report each hop with its file and line. Verify that every hop is marked resolved or one of a set, and say which hops are candidates rather than confirmed.

Caveat. The README benchmarks cover Java and TypeScript only, so Python, JavaScript and C# results are not measured there.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page