graph-code
Installation
SKILL.md
Codex compatibility note:
- Invoke
$skill-name: load the registered.agents/skills/<name>/SKILL.mdand execute it with Codex tools; no separateSkilltool or Claude mode switch is needed. Author.claude/**; mirrors are generated.- Track steps before execution and keep progress/evidence current. Explicit skill requests execute their protocol. Use the native question tool for required questions.
- Map foreign tool names to available host capabilities. A name mismatch needs no approval; an actually unavailable required capability stops with its step/evidence and a user question before adaptation.
- Subagent authorization: when a skill is user-invoked or AI-detected and its protocol requires subagents, that skill activation authorizes use of the required
spawn_agentsubagent(s) for that task.- Preserve protocol order unless the user approves a deviation. Workflows use
$start-workflow: gates stay fixed; other steps may flex with logged reasons and evidence. [BLOCKING] Mode routing — detect FIRST. The mode is--mode=build|query|trace|blast-radius|connect-api|export, or the first argument when it is exactly one of those six words ($graph-code export --format=mermaid <file>). Everything after the mode is that mode's own arguments (--scope=,--direction,--node-mode,--format=,--json, a target). Read the mode file in full before anything else (see Mode Dispatch). Each of the six modes works called directly with no workflow.
Quick Summary
Goal: [Code Intelligence] Operate the structural code knowledge graph (Tree-sitter nodes and edges in .code-graph/graph.db, SQLite) through the python .claude/scripts/code_graph CLI: build or sync it, query relationships, trace system flow, analyze the blast radius of a change, match frontend calls to backend routes, and export JSON snapshots or single-file Mermaid diagrams.
Workflow: Detect the mode → read its references/mode-<x>.md in full → run the CLI live → report the JSON result with file:line evidence.
Key Rules: