メニュー
Use when you need blast-radius analysis, change safety checks, or to know what depends on a function, type, or file before editing. Keywords: impact, blast radius, what breaks, safety, dependents, risk.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Work in the build area — 66 symbols across 11 files (57% cohesion)
Work in the get area — 37 symbols across 12 files (27% cohesion)
Work in the glyph-canvas area — 41 symbols across 1 files (48% cohesion)
Work in the js area — 27 symbols across 1 files (36% cohesion)
Work in the src area — 31 symbols across 3 files (87% cohesion)
Work in the tests area — 38 symbols across 3 files (46% cohesion)
| name | gortex-impact |
| description | Use when you need blast-radius analysis, change safety checks, or to know what depends on a function, type, or file before editing. Keywords: impact, blast radius, what breaks, safety, dependents, risk. |
| argument-hint | symbol or change to assess |
mcp_gortex_smart_context or mcp_gortex_plan_turn to identify the target symbols.mcp_gortex_get_dependents on the symbol you plan to change.mcp_gortex_get_edit_plan when multiple related symbols may need coordinated edits.activate_change_impact_analysis_tools for richer impact verification and diff-aware analysis.activate_symbol_analysis_and_usage_tools to map usages and likely test targets.mcp_gortex_get_communities often indicate hidden coordination cost.mcp_gortex_get_processes reveal runtime effects not obvious from a single file.what breaks if we change glyph compile schedulingimpact of changing change-bridge layer normalizationis it safe to rename this outline-editor helper