Goal: route only. Do not perform the task. Always return an exact invocation the user can copy-paste.
If $ARGUMENTS is empty, return this menu:
Skills (slash commands):
/ix-understand <target> — architectural mental model of a repo, subsystem, or file
/ix-investigate <symbol> — deep dive on one symbol, class, or feature
/ix-impact <target> — blast radius and risk before editing
/ix-plan <targets...> — risk-ordered multi-file change plan
/ix-debug <symptom> — root-cause analysis for a bug or failure
/ix-architecture [scope] — design health, coupling, and structural smells
/ix-docs <target> — onboarding or reference documentation
Direct tool calls (for quick lookups):
ix-query — look up a symbol by exact name
ix-locate — search by text pattern or keyword
ix-explain — full role, importance, and caller details for a symbol
ix-neighbors — callers, callees, and dependencies
ix-impact — blast radius for a file or symbol
ix-trace — full execution path trace
ix-rank — top symbols by dependents, callers, or members
ix-subsystems — all subsystems with file counts and hierarchy
ix-inventory — enumerate files or symbols in a path scope
ix-stats — graph-wide statistics and health
ix-smells — architecture smell detection
ix-map — architectural overview with subsystem table
ix-ingest — graph status and refresh trigger
ix-decide — pre-edit policy verdict (ALLOW / REVIEW / BLOCK)
ix-health — CLI and graph availability check
If $ARGUMENTS is non-empty, classify the request and recommend exactly one best starting point:
Architecture, onboarding, "how does X work", system overview:
/ix-understand <target>
Symbol deep dive, "what does X do", feature internals, implementation details:
/ix-investigate <target>
Pre-edit risk, blast radius, "what breaks if I change X":
/ix-impact <target>
Multi-file change, refactor, migration, implementation plan:
/ix-plan <targets or change description>
Bug, failure, regression, unexpected behavior, error message:
/ix-debug <symptom>
Design quality, complexity, coupling, smells, architecture health:
/ix-architecture <scope>
Documentation, onboarding guide, reference docs:
/ix-docs <target>
Simple lookup requests (use tools directly, not skills):
- Where is X defined (exact name) ->
ix-query with symbol: "X"
- Search for X by text or pattern ->
ix-locate with pattern: "X"
- Who calls X ->
ix-neighbors with symbol: "X", direction: "callers"
- What does X call ->
ix-neighbors with symbol: "X", direction: "callees"
- Full call chain through X ->
ix-trace with symbol: "X"
- What files are under a path ->
ix-inventory with path: "src/...", kind: "file"
- Top symbols by dependents ->
ix-rank with by: "dependents"
- Architecture smells ->
ix-smells
- Is the graph ready? ->
ix-health
Output format:
Best start: <one sentence>
Run: <exact slash command or tool call>
Why: <one short sentence>
If the request is ambiguous, make the safest routing choice and note what target placeholder to replace.
1---2name: ix-help-33description: Route to the right Ix skill or tool for the current task. Route only; do not perform the task.4metadata:5 source: https://skillmd.com/skills/ix-infrastructure/ix-help-36 openclaw:7 requires:8 bins:9 - ix10---1112Goal: route only. Do not perform the task. Always return an exact invocation the user can copy-paste.1314If `$ARGUMENTS` is empty, return this menu:1516**Skills (slash commands):**17- `/ix-understand <target>` — architectural mental model of a repo, subsystem, or file18- `/ix-investigate <symbol>` — deep dive on one symbol, class, or feature19- `/ix-impact <target>` — blast radius and risk before editing20- `/ix-plan <targets...>` — risk-ordered multi-file change plan21- `/ix-debug <symptom>` — root-cause analysis for a bug or failure22- `/ix-architecture [scope]` — design health, coupling, and structural smells23- `/ix-docs <target>` — onboarding or reference documentation2425**Direct tool calls (for quick lookups):**26- `ix-query` — look up a symbol by exact name27- `ix-locate` — search by text pattern or keyword28- `ix-explain` — full role, importance, and caller details for a symbol29- `ix-neighbors` — callers, callees, and dependencies30- `ix-impact` — blast radius for a file or symbol31- `ix-trace` — full execution path trace32- `ix-rank` — top symbols by dependents, callers, or members33- `ix-subsystems` — all subsystems with file counts and hierarchy34- `ix-inventory` — enumerate files or symbols in a path scope35- `ix-stats` — graph-wide statistics and health36- `ix-smells` — architecture smell detection37- `ix-map` — architectural overview with subsystem table38- `ix-ingest` — graph status and refresh trigger39- `ix-decide` — pre-edit policy verdict (ALLOW / REVIEW / BLOCK)40- `ix-health` — CLI and graph availability check4142If `$ARGUMENTS` is non-empty, classify the request and recommend exactly one best starting point:4344- Architecture, onboarding, "how does X work", system overview:45 `/ix-understand <target>`4647- Symbol deep dive, "what does X do", feature internals, implementation details:48 `/ix-investigate <target>`4950- Pre-edit risk, blast radius, "what breaks if I change X":51 `/ix-impact <target>`5253- Multi-file change, refactor, migration, implementation plan:54 `/ix-plan <targets or change description>`5556- Bug, failure, regression, unexpected behavior, error message:57 `/ix-debug <symptom>`5859- Design quality, complexity, coupling, smells, architecture health:60 `/ix-architecture <scope>`6162- Documentation, onboarding guide, reference docs:63 `/ix-docs <target>`6465- Simple lookup requests (use tools directly, not skills):66 - Where is X defined (exact name) -> `ix-query` with `symbol: "X"`67 - Search for X by text or pattern -> `ix-locate` with `pattern: "X"`68 - Who calls X -> `ix-neighbors` with `symbol: "X"`, `direction: "callers"`69 - What does X call -> `ix-neighbors` with `symbol: "X"`, `direction: "callees"`70 - Full call chain through X -> `ix-trace` with `symbol: "X"`71 - What files are under a path -> `ix-inventory` with `path: "src/..."`, `kind: "file"`72 - Top symbols by dependents -> `ix-rank` with `by: "dependents"`73 - Architecture smells -> `ix-smells`74 - Is the graph ready? -> `ix-health`7576Output format:77```text78Best start: <one sentence>79Run: <exact slash command or tool call>80Why: <one short sentence>81```8283If the request is ambiguous, make the safest routing choice and note what target placeholder to replace.