Menú
Load codebase context from knowledge graph instead of scanning raw files
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Manage OMA skills — list, add, remove, search, and edit skills
Socratic deep interview with mathematical ambiguity gating before autonomous execution
Remove AI slop - low-quality, generic, or verbose content. Use for "clean up", "remove fluff", and "make concise".
Consensus planning - agree before executing. Use for "ralplan", "consensus", "pre-execution review".
Setup routing and environment configuration. Use for "setup", "configure", and "get started".
N coordinated agents on shared task list using Claude Code native teams, with git worktree isolation per executor
| name | graph-context |
| description | Load codebase context from knowledge graph instead of scanning raw files |
| trigger | auto (injected by session-start when graph provider is configured) |
A knowledge graph has been built for this project. Use it instead of scanning raw files.
If graphwiki-out/ exists:
graphwiki path <nodeA> <nodeB> for structural queries (0 extra tokens)| Command | Use When |
|---|---|
graphwiki query "<question>" | General questions about the codebase |
graphwiki path <nodeA> <nodeB> | How two modules/concepts connect |
graphwiki status | Check graph health and drift score |
graphwiki lint | Find contradictions in the graph |
graphwiki build . --update | After changing files (incremental) |
graphwiki build . --resume | Resume a crashed/interrupted build |
graphwiki ingest <file> | Add a new file to the graph |
graphwiki benchmark "<question>" | Measure token cost of a query |
raw/ (immutable source files)graphwiki-out/ (auto-generated output)If graphify-out/ exists:
| Command | Use When |
|---|---|
/graphify query "<question>" | General codebase questions (BFS) |
/graphify query "<question>" --dfs | Trace a specific path (DFS) |
/graphify path "<nodeA>" "<nodeB>" | Shortest path between two concepts |
/graphify explain "<node>" | Understand what a specific node does |
/graphify . | Full rebuild of the knowledge graph |
/graphify . --update | Incremental rebuild (changed files only) |
/graphify . --wiki | Generate agent-crawlable wiki output |
/graphify add <url> | Fetch and add a URL to the graph |
/graphify . --watch | Auto-rebuild on file changes |
/graphify . --mcp | Start MCP stdio server for agent access |
graphify-out/ (auto-generated output)graphify-out/graph.json is for programmatic traversal only. Use query/path commands.The entire point of using a graph provider is to avoid re-reading raw source files every session. A 50-file codebase costs ~100K+ tokens to read raw. The graph reduces this to ~2-5K tokens per query.
Do NOT fall back to reading raw files unless the graph explicitly lacks the information needed.
graphwiki is included as an optional dependency of OMA. If not available, install manually: npm install -g graphwiki