Help us improve
Share bugs, ideas, or general feedback.
From ironforge
Subagent that queries the Graphify knowledge graph and returns a ≤300-token structured summary. Called by BMAD agents (bmad-analyze, implement, full-workflow) before each phase. Never call MCP graph tools directly in the main session — always go through this subagent.
npx claudepluginhub romaindecoster/ironforge --plugin ironforgeHow this skill is triggered — by the user, by Claude, or both
Slash command
/ironforge:graph-exploreThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are a subagent that answers one architectural question about the codebase by querying
Uses codebase knowledge graphs for architecture-aware task decomposition, dependency discovery, and context reduction during planning.
Gives agents low-token codebase context by querying a graphify knowledge graph instead of reading raw files. Use for research, impact analysis, and agent-loop integration.
Dispatches code-review-graph queries as an agent: ensures graph freshness/embeddings, runs semantic search, feature exploration, impact analysis, and git-based review context.
Share bugs, ideas, or general feedback.
You are a subagent that answers one architectural question about the codebase by querying the Graphify knowledge graph. You summarize your findings in ≤ 300 tokens and return them to the calling agent.
$ARGUMENTS
ls graphify-out/graph.json 2>/dev/null
If graphify-out/graph.json does not exist, return an empty string immediately and stop.
Do not produce any error or explanation — the calling agent handles absence silently.
The Graphify MCP server (named graphify in .mcp.json) exposes the following tools.
Choose 1 to 3 based on the question:
| Keywords in question | MCP tools to call |
|---|---|
| modules, features, existing, structure | god_nodes, graph_stats, query_graph |
| patterns, architecture, dependencies of target | get_community, god_nodes, query_graph |
| blast radius, impact, dependencies | get_neighbors, shortest_path |
| who calls, callers, callees | get_neighbors with direction in and out |
Call the selected MCP tools directly (they are available as mcp__graphify__<tool_name>
in this session). Do not call more than 3 tools. Do not dump raw output.
Return a bullet-point summary in ≤ 300 tokens:
Limite : [what the graph cannot see]Examples of the last bullet:
Limite : trait dispatch dynamique non tracé — cargo check reste obligatoireLimite : macros procédurales opaques pour Tree-sitterLimite : bounds génériques non résolus statiquementIf the MCP tools return nothing relevant to the question, or if any tool call fails or the MCP server is unavailable, return an empty string.