CodexClaude CodeCursorHermes Agent
Back to Tools
skill · tool profile
Graphify
AI coding assistant skill (Claude Code, Codex, OpenCode, Cursor, Gemini CLI, and more). Turn any folder of code, SQL schemas, R scripts, shell scripts, docs, papers, images, or videos into a queryable knowledge graph. App code + database schema + infrastructure in one graph.
skill CodexClaude CodeCursorHermes Agent
01
At a glance.
A compact read before the deeper capability notes and official setup links.
02
Core features.
Feature cards focus on what the tool helps users do, not generated setup commands.
Type /graphify in your AI coding assistant and it maps your entire project — code, docs, PDFs, images, videos — into a knowledge graph you can query instead of grepping through files.
Works in Claude Code, Codex, OpenCode, Cursor, Gemini CLI, GitHub Copilot CLI, VS Code Copilot Chat, Aider, OpenClaw, Factory Droid, Trae, Hermes, Kimi Code, Kiro, Pi, and Google Antigravity.
Step 2 — register the skill with your AI assistant:
Codex uses $graphify instead of /graphify.
On platforms that support payload-bearing hooks (Claude Code, Gemini CLI), a hook fires automatically before search-style tool calls and nudges your assistant toward the graph path.
On the others (Codex, OpenCode, Cursor, etc.), the persistent instruction files (AGENTS.md, .cursor/rules/, etc.) provide the same query-first guidance.
GRAPHREPORT.md is still available for broad architecture review.
God nodes — the most-connected concepts in your project.
04
Agent / Skill / MCP / Workflow fit.
This panel keeps technical format separate from the user-facing AI category.
05
Official setup path.
Generated install snippets are intentionally not mirrored here because they drift. The page links to source-owned setup docs instead.
06
Evidence and adoption notes.
These notes help a user decide whether to investigate the official project further.
Source repository last pushed at 2026-05-18T11:09:39Z.
Generated from source metadata; confirm operational details in the official project before adopting it.
Review the upstream license, maintenance activity, and issue history before using it in production.
Trusted source