codegraph
Skill11 starsChanged 10 days agoMITView on GitHub
Pre-indexed code knowledge graph for codebase exploration, symbol navigation, call chains, and change-impact analysis. Use when exploring an unfamiliar repo, tracing callers/callees, or assessing blast radius before a change — replaces grep+Read loops with one query.
16 other projects use a version of this.
Adopted by
Most recently taken up by
- aiproxer/aiproxertheir own version, first seen Nov 8, 2026
- davidgfolch/AI-job-searchtheir own version, first seen Nov 8, 2026
- rakaarwaky/agents-arwakytheir own version, first seen Nov 1, 2026
- whoaskedssselery/claude-workspacetheir own version, first seen Oct 20, 2026
- seanb4t/codegraph-gotheir own version, first seen Oct 17, 2026
- gandolh/my-personal-skillstheir own version, first seen Oct 17, 2026
Other versions16 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 16
- idaholab/moose★ 2.4ksame name
- alibaba/neug★ 177same name
- SylphAI-Inc/skills★ 111same name
- aiproxer/aiproxer★ 22same name
- sunerpy/codegraph-rust★ 20same name
- linkpranay-ai/context-engineering-protocol★ 9same name
- davidgfolch/AI-job-search★ 6same name
- sponge-b0b/Polaris★ 4same name
- betterlmy/agent-skills★ 3same name
- full-stack-skills/agent-skills★ 2same name
6 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository20 other files it gives its agents.
- codebase-designSkill
- code-reviewSkill
- diagnosing-bugsSkill
- domain-modelingSkill
- grillingSkill
- grill-meSkill
- grill-with-docsSkill
- handoffSkill
- implementSkill
- improve-codebase-architectureSkill
- paseo-workloopSkill
- requirement-ledgerSkill
- retroSkill
- setup-matt-pocock-skillsSkill
- tddSkill
- to-specSkill
- to-ticketsSkill
- wait-whatSkill
- workloop-auditSkill
- writing-for-agentsSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 13 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 36
Never use grep to verify codegraph results — AST edges are stronger evidence than text matches.
- Distinctive: line 38
After edits, watch the staleness banner (⚠️ names a pending file) — Read that file directly for live content.
“Common” is measured: kept by at least 6 in 10 of the 13 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
CodeGraph
SQLite knowledge graph of a codebase's symbols, edges, and files (30+ languages), served over MCP. One codegraph_explore call returns the verbatim, line-numbered source of the relevant symbols plus the call paths between them and a blast-radius summary.
Setup (per project)
codegraph init # builds .codegraph/ index in cwd (needed before MCP tools work there)
codegraph status # index health; pending-sync files are listedAuto-sync keeps the index fresh: the OS-native file watcher + 2s debounce, per-file staleness banners, and catch-up reconciliation on MCP reconnect. Manual codegraph sync is only needed with CODEGRAPH_NO_DAEMON=1 or CI pre-flight.
MCP tools
| Intent | Tool |
| Almost any question — architecture, flow, bug, investigation | codegraph_explore ⭐ (primary; usually the only call needed) |
| Locate symbol by name | codegraph_search |
| Call chain | codegraph_callers / codegraph_callees |
| Change impact | codegraph_impact |
| Single symbol full source / overload disambiguation | codegraph_node |
| File structure | codegraph_files |
| Index health | codegraph_status |
Principles
codegraph_explorefirst — it groups source by file with line numbers and links the call paths.- Answer directly from the graph; do NOT delegate exploration to file-reading subagents — that defeats the index.
- One
explorebeatssearch+nodechained calls. - Never use grep to verify codegraph results — AST edges are stronger evidence than text matches.
- Graph edges are proven, not complete: a missing edge does not prove a reference is absent.
- After edits, watch the staleness banner (⚠️ names a pending file) — Read that file directly for live content.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.