Who it is forA developer who has just joined a team or inherited a repo and needs the layout before making changes.
The problemReading files one by one is slow, and it is hard to see which concepts and subsystems matter most.
The outcomeA graph.html you can click through, a GRAPH_REPORT.md listing key concepts and suggested questions, and a graph.json for later queries.
What you need first
- Python 3.10 or newer
- uv (recommended) or pipx
- A supported AI coding assistant, such as Claude Code, Cursor, Codex, or Gemini CLI
- A local copy of the repository you want to map
Steps
- Run
uv tool install graphifyy(orpipx install graphifyy) to install the CLI. - Run
graphify installonce so it registers the skill with your assistant. - Open your AI assistant in the repository and type
/graphify . - Open
graphify-out/graph.htmlin a browser and readgraphify-out/GRAPH_REPORT.md.
Prompt for your agent
In the Graphify-Labs/graphify repo setup, run `/graphify <repo-path>` on the target repository at <repo-path>. Confirm that graphify-out/ contains graph.html, GRAPH_REPORT.md, and graph.json, then summarize the top concepts listed in GRAPH_REPORT.md.
Caveat. Code parsing is local and deterministic, but docs, PDFs, and media use your assistant's model or a configured API key for the semantic pass.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: 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