Menü
Route to the right Ix skill or command for your task
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Analyze system design — structure, coupling, code smells, and high-risk hotspots. Purely graph-based, no code reads.
Root cause analysis — trace execution path to a failure, narrow candidates, read minimal source only at suspected failure points.
Generate narrative-first, importance-weighted documentation for a repo, system, or subsystem with a selective reference layer. Use --full for deeper module/class/method coverage.
Change risk analysis — blast radius, affected systems, and what to test. Depth scales with risk level; low-risk targets stop early.
Deep dive into a symbol, feature, or bug. Graph-first, minimal code reads, early stopping when sufficient evidence found.
Generate a risk-ordered implementation plan for a set of targets. Assesses blast radius per target, finds data flows between them, and produces a safe change sequence.
| name | ix-help |
| description | Route to the right Ix skill or command for your task |
| argument-hint | <task or question> |
This skill routes the user to the best Ix entry point and then stops.
You must not:
ix commandsIf $ARGUMENTS is empty, return this menu:
ix-understand <target> — architectural mental modelix-investigate <symbol> — deep dive on one symbol or featureix-impact <target> — blast radius before editingix-plan <targets...> — risk-ordered multi-file change planix-debug <symptom> — root-cause analysis for bugsix-architecture [scope] — design health and structural smellsix-docs <target> — onboarding or reference documentationix commands — direct lookups like ix locate <symbol> --format llmIf $ARGUMENTS is non-empty, classify the request and recommend exactly one best starting point:
ix-understand <target>ix-investigate <target>ix-impact <target>ix-plan <targets or change description>ix-debug <symptom>ix-architecture <scope>ix-docs <target>ix locate <symbol> --format llmix text "<term>" --limit 10 --format llmix callers <symbol> --limit 15 --format llmix callees <symbol> --limit 15 --format llmix inventory --kind file --path <path> --format llmReturn exactly this block and nothing else:
Best start: <one sentence describing the recommended entry point>
Run: <exact copy-paste skill invocation or ix command>
Why: <one short sentence>
If the request is ambiguous, make the safest routing choice and say which placeholder to replace.