safishamsi/graphify

Updated top 10 as of 4/13/26 (GitHub stars + X/Reddit buzz, focused on folder-to-KG/wiki like Karpathy's workflow): 1. safishamsi/graphify (~19k ⭐) - Still #1. One-command folder → navigable KG + Obsidian vault + backlinks. 71x token efficiency. 2. GitNexus (25k ⭐) - Browser-based code KG with visual mapping. 3. kepano/obsidian-skills (20k+ ⭐) - Obsidian enhancer for LLM wikis. 4. domleca/llm-wiki - Obsidian plugin: entity extraction, local Ollama Q&A, auto-wiki pages. 5. ussumant/llm-wiki-compiler - Markdown compiler to topic wiki. 6. atomicmemory/llm-wiki-compiler - Interlinked Obsidian-style output. 7. skyllwt/OmegaWiki - PKL/social network of KGs. 8. jmagly/aiwg - Agentic wiki builder. 9. PageFly (custom) - Multi-format ingest + API-queryable KG. 10. Custom Karpathy gist + Grok API - Model-agnostic; Grok excels at structured compilation/linting (use xAI API for file-aware agents). Graphify + Obsidian + Grok API combo works best for me—fast reasoning, no vendor lock-in. Stars shift fast; check repos for latest.

Contains the exact GitHub repo slug.

It doesn't remember what you did with it. That's the missing half. Opened an integration proposal last week: github.com/safishamsi/graphi… The idea: graphify's structural graph feeds agentmemory's context injection. agentmemory's temporal data (which files you debugged, what decisions you made, what broke) weights graphify's nodes by actual developer activity. Structural knowledge + temporal memory. One tells you "auth.ts imports jwt.ts, belongs to auth community." The other tells you "you refactored auth.ts 3 days ago, switching from jsonwebtoken to jose." Both open source. Both composable.

Returned by a high-confidence repo query and contains a visible project phrase, but the exact URL, slug, or package name was not visible.