القائمة
Use when navigating or auditing the docs/ knowledge graph — explain a doc's links, find the path between two docs, or surface god nodes / bridges / orphans.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Root-cause native Bannerlord CTDs (AccessViolation in TaleWorlds.Native.dll) via Event Log offsets, offline disassembly, and live debugger forensics. No symbols needed.
Dispatch an independent Codex verification job directly via `codex exec` Bash call, then retrieve and present results
Inspect all changed files, group by logical concern, and guide atomic per-concern commits following TAOM's 50/72 rule and commit trailer convention.
Load a snapshot saved by /context-save and present it so this session can pick up where the last one left off without re-deriving decisions.
Launch parallel deep-dive agents to review completed work for quality, standards, compatibility, completeness, and cross-system data flow
Respond to a Bannerlord engine update (Steam force-bump or deliberate migration) — preserve the decompile baseline, regen, diff, re-verify bindings and creature data, control-battle.
| name | doc-graph |
| description | Use when navigating or auditing the docs/ knowledge graph — explain a doc's links, find the path between two docs, or surface god nodes / bridges / orphans. |
| allowed-tools | Bash, Read |
| argument-hint | ["explain <doc> | path <a> <b> | metrics"] |
Query + audit TAOM's documentation knowledge graph via tools/graph_query.py. This is ADR-010 Phase 5 (graph analytics over the link graph). Authoritative reference + interpretation guide: docs/features/doc-graph.md — read it for what the metrics mean and the scope boundaries; this skill is just the entry point.
The tool is deterministic and offline (reads only the markdown links already in docs/). .md nodes only — Serena owns C# symbols, the taom-moduledata MCP owns game-data refs.
Two modes — Navigate (mid-task, token-cheap) and Audit (periodic KB hygiene). Concrete triggers:
explain Xpath A B --directedexplain X/knowledge-compile, feature wave) — did any ship orphaned? → metrics/skill-stocktake for docs → metrics --top 15Not for full-text search (grep / INDEX.md), C# symbols (Serena), or game-data refs (taom-moduledata MCP). Full use-case table + "when NOT to use it": docs/features/doc-graph.md.
python tools/graph_query.py explain <doc> # inbound + outbound neighbours
python tools/graph_query.py path <a> <b> --directed # forward link chain (prefer --directed)
Name a doc by slug (career-system), filename, or repo-relative path. Use --directed for path — undirected routes through the INDEX.md super-hub and reports a misleading "2 hops through INDEX" for almost any pair.
python tools/graph_query.py metrics --top 15 (or --summary for counts only). Read the output.INDEX.md — features/X.md means X has no peer cross-links; reinforce it from a sibling doc/RCA..md link; link into INDEX/a sibling, or delete.tools/build_backlinks.py + /lint-docs to refresh + confirm, and re-run metrics to verify the signal moved.--infer / memory-layer / MCP ideas — they're documented as future phases in the feature doc and were intentionally not built.python tools/graph_query.py … directly (verbs accept --json).