ix-architecture
Analyze system design — structure, coupling, code smells, and high-risk hotspots. Purely graph-based, no code reads.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Analyze system design — structure, coupling, code smells, and high-risk hotspots. Purely graph-based, no code reads.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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.
Build a detailed architectural mental model of a system, subsystem, or the whole repo. Graph-first, source reads only when needed for data flow or key patterns.
| name | ix-architecture |
| description | Analyze system design — structure, coupling, code smells, and high-risk hotspots. Purely graph-based, no code reads. |
Strip --save and any following path token from $ARGUMENTS before processing the scope.
--save <path> is present, set SAVE_PATH to that path.--save is present without a path, auto-generate ix-architecture-<scope-slug>.md in cwd (scope slug = $ARGUMENTS with spaces and slashes replaced by -, or repo if arguments are empty).--save is absent, SAVE_PATH is empty — do not write a file.Before anything else, run:
command -v ix
ix status
If either fails, stop: "ix graph unavailable — run ix connect or check your connection."
Then verify the graph has data:
ix subsystems --list --format llm
If the result is empty or returns an error, stop: "No graph data yet — run ix map to build the graph first."
ix briefing --format json 2>&1
If it returns JSON with a revision field, Pro is available. Note recentDecisions for use below. Skip all [Pro] steps if it errors.
ix subsystems --format llm
Filter results to $ARGUMENTS scope if provided (match on subsystem name or path prefix). Store the full output as SUBSYSTEMS.
Early-stop gate: Examine each region's metrics. If ALL of the following are true across every region:
cohesion > 0.7coupling < 0.4crosscut_score ≤ 0.1 (or field absent)confidence ≥ 0.6→ Report "System appears structurally healthy — no significant coupling, cohesion, or crosscutting issues detected." List subsystems with their metrics and stop. Do not proceed to Phase 2.
ix smells --format llm
Filter to scope if $ARGUMENTS was provided. Store as SMELLS.
Health gate — choose one path:
Inline path (all must be true):
god-module smell presentcrosscut_score > 0.1→ Synthesize the report inline using SUBSYSTEMS + SMELLS. Proceed to Phase 3 only if needed (see below). Skip delegation.
Delegate path (any is true):
god-module smell is presentcrosscut_score > 0.1→ Spawn the ix-architecture-auditor agent. Pass SUBSYSTEMS and SMELLS directly in the agent prompt so it can skip its own Steps 1–4 (subsystem + smell collection). Include the scope from $ARGUMENTS. Relay the agent's complete output to the user, then skip to the [Pro] Cross-reference decisions step.
Run ix rank only if at least one of the following is true:
god-module smell exists in SMELLS (even on the inline path)SUBSYSTEMS has coupling > 0.5ix rank --by dependents --kind class --top 10 --exclude-path test --format llm
Identify the top-ranked components that overlap with smell findings or high-coupling regions. Include these as hotspots in the inline report.
If neither condition is met, skip ix rank entirely.
When taking the inline path, produce:
Summary — one sentence verdict on overall health.
Subsystem overview — table of regions with cohesion, coupling, crosscut_score.
Smells — list each smell with affected symbol and severity.
Hotspots — (if Phase 3 ran) top-ranked components that coincide with smells or high-coupling regions.
Recommended action — one concrete next step.
If Pro is available, after the report (inline or delegated) is complete:
ix decisions --format json
Append a Recorded Decisions section cross-referencing relevant design decisions against the findings — especially decisions that affect god-modules, high-coupling regions, or identified hotspots.
Only if SAVE_PATH is non-empty (i.e., --save was passed):
SAVE_PATH using the Write tool.Saved to <SAVE_PATH>.--save was not passed.