菜单
Blast-radius analysis for a symbol or file — shows all callers, type supertypes/subtypes, and reference count before you change it. Use when refactoring, deleting, or changing the signature of any function, type, or method. Also accepts a file path to surface all exported-symbol impact in one shot.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/TuYv/ccpm --skill lsp-impact命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
Use when auditing a paid ad account for incremental contribution, wasted spend, or measurement integrity before scaling; runs a typed 20-item ROAS profile with verified vetoes and a SHIP/FIX/BLOCK/UNDECIDED gate on own exported data. Not for campaign structure design — use campaign-architect; not for creative production — use ad-creative-builder. 付费广告账户审计/ROAS评分
Use when the user asks to "write ad copy", "generate RSA headlines", or "build ad creative at volume"; produces ad units — RSA headlines/descriptions, hooks, and an angle matrix — message-matched to the destination landing page. Not for scoring an ad account — use ad-account-auditor; not for the post-click page — use landing-optimizer; not for organic articles — use content-writer. 广告创意/广告文案/RSA标题
Use when the user asks to "design an A/B test", "set up a creative/landing test", "run an incrementality test", or "is this result statistically and practically material?"; produces a hypothesis, variant matrix, sample-size/duration/power plan, and a documented effect/uncertainty read from own exported results. It applies only a precommitted owner-approved action rule; the statistical helper never chooses a business action. Not for producing variants — use ad-creative-builder; not for reading back one shipped change — use paid-measurement-loop. 广告AB测试设计/实验设计/显著性判定/增效测试
| name | lsp-impact |
| description | Blast-radius analysis for a symbol or file — shows all callers, type supertypes/subtypes, and reference count before you change it. Use when refactoring, deleting, or changing the signature of any function, type, or method. Also accepts a file path to surface all exported-symbol impact in one shot. |
| argument-hint | [symbol-name | file-path] |
| user-invocable | true |
| allowed-tools | mcp__lsp__go_to_symbol mcp__lsp__find_callers mcp__lsp__type_hierarchy mcp__lsp__find_references mcp__lsp__get_server_capabilities mcp__lsp__blast_radius |
| license | MIT |
| compatibility | Requires the agent-lsp MCP server (github.com/blackwell-systems/agent-lsp) |
| metadata | {"required-capabilities":"referencesProvider","optional-capabilities":"callHierarchyProvider typeHierarchyProvider workspaceSymbolProvider"} |
Requires the agent-lsp MCP server.
Blast-radius analysis for any symbol or file. Discovers all direct references, callers (via call hierarchy), and type relationships before you touch anything. Read-only — does not modify any files.
Run this skill before lsp-edit-export: impact tells you what exists and how widespread the change is; lsp-edit-export tells you how to execute the change safely.
Invocation:
"internal/lsp/client.go") → use the File-level entry (Step 0) to surface all exported-symbol impact at once."codec.Encode", "Buffer.Reset") → skip Step 0; start at Prerequisites, then Step 1.Use this shortcut when the user is changing or auditing an entire file rather
than a single symbol. blast_radius enumerates all exported symbols in
the file, resolves their references, and returns test callers (with enclosing
test function names) and non-test callers in a single call.
mcp__lsp__blast_radius({
"changed_files": ["/abs/path/to/file.go"],
"include_transitive": false // set true to surface second-order callers
})
Returns:
affected_symbols — each exported symbol with its reference counttest_callers — test files + enclosing test function namesnon_test_callers — production call sitesDecision after Step 0:
| Result | Action |
|---|---|
| 0 non-test callers | Low blast radius. Proceed with change. |
| Few callers, known files | Medium risk. Update each call site. |
| Many callers across packages | High risk. Consider staged rollout. |
| Want symbol-level detail | Continue to Steps 1–5 for any specific symbol. |
Skip Steps 1–5 if the file-level summary is sufficient.
If LSP is not yet initialized, call mcp__lsp__start_lsp with the workspace
root first.
Check what the server supports before proceeding — find_callers and
are optional LSP features not implemented by all servers:
基于 SOC 职业分类
type_hierarchymcp__lsp__get_server_capabilities()
Note which tools appear in supported_tools. Steps 3 and 4 below depend on
this result.
Use go_to_symbol with the symbol name provided by the user:
mcp__lsp__go_to_symbol({
"symbol_path": "Package.SymbolName",
"workspace_root": "/abs/path" // optional, narrows scope
})
→ returns: file, line, column (1-indexed)
symbol_path uses dot notation. For a top-level function Encode in package
codec, use "codec.Encode". For a method Reset on type Buffer, use
"Buffer.Reset".
Record the returned file, line, and column — you will pass them to
every subsequent step.
Call find_references with include_declaration: false to find every usage
site across the workspace:
mcp__lsp__find_references({
"file_path": "<file from Step 1>",
"position_pattern": "func @@SymbolName(", // adjust prefix for symbol kind
"include_declaration": false
})
Collect all reference locations. Group results by file. Record the total count and list of files — these feed the Impact Report.
See references/patterns.md for position_pattern
examples by language and symbol kind.
Only if find_callers appears in supported_tools from Step 0.
mcp__lsp__find_callers({
"file_path": "<file from Step 1>",
"line": <line from Step 1>,
"column": <column from Step 1>,
"direction": "incoming" // use "both" if callees are also needed
})
If find_callers is not in supported_tools, skip this step entirely.
Note "call hierarchy not supported by this server" in the Impact Report.
Only applicable when the symbol is a type, interface, or class (not a
plain function or method). Only if type_hierarchy appears in supported_tools.
mcp__lsp__type_hierarchy({
"file_path": "<file from Step 1>",
"line": <line from Step 1>,
"column": <column from Step 1>,
"direction": "both"
})
If the symbol is a function or method: skip this step; note
"not applicable (function)" in the report.
If type_hierarchy is not in supported_tools: skip this step; note
"not supported by this server" in the report.
Produce the Impact Report using the format defined in references/patterns.md.
Include:
find_callers incoming (or skip note)type_hierarchy (or skip note)Then apply the decision guide:
| Blast radius | Recommendation |
|---|---|
| 0 references | Likely dead code. Confirm with lsp-dead-code before deleting. |
| 1–5 files | Low risk. Proceed. Update all callers. |
| 6–20 files | Medium risk. Plan changes carefully. Stage in waves. |
| > 20 files | High risk. Consider a deprecation path or feature flag. |
Goal: assess blast radius of exported function `ParseConfig` in pkg/config
Prerequisites — get_server_capabilities:
→ supported_tools: [go_to_symbol, find_references, find_callers, ...]
→ type_hierarchy: not in supported_tools
Step 1 — go_to_symbol: symbol_path="config.ParseConfig"
→ pkg/config/parser.go:42:6
Step 2 — find_references: position_pattern="func @@ParseConfig("
→ 7 references in 4 files
→ cmd/main.go, internal/app.go, internal/loader.go, pkg/config/parser_test.go
Step 3 — find_callers: direction="incoming"
→ callers: cmd.main (cmd/main.go:14), app.Start (internal/app.go:31), ...
Step 4 — type_hierarchy: skipped (function), also not supported by server
Step 5 — Impact Report:
## Impact Report: ParseConfig
- Kind: function
- Definition: pkg/config/parser.go:42:6
- References: 7 across 4 files
...
- Risk level: low
position_pattern with @@ is a agent-lsp extension. If your MCP client
does not support it, fall back to explicit line and column parameters from
the location returned by go_to_symbol in Step 1.