菜单
Extract a selected code block into a named function. Primary path uses the language server's extract-function code action; falls back to manual extraction when no code action is available. Validates captured variables, scope shadowing, and compilation after extraction.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/TuYv/ccpm --skill lsp-extract-function命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| name | lsp-extract-function |
| description | Extract a selected code block into a named function. Primary path uses the language server's extract-function code action; falls back to manual extraction when no code action is available. Validates captured variables, scope shadowing, and compilation after extraction. |
| argument-hint | [file-path] [start-line] [end-line] [new-function-name] |
| user-invocable | true |
| allowed-tools | mcp__lsp__list_symbols mcp__lsp__suggest_fixes mcp__lsp__execute_command mcp__lsp__apply_edit mcp__lsp__get_diagnostics mcp__lsp__open_document mcp__lsp__format_document mcp__lsp__get_server_capabilities |
| license | MIT |
| compatibility | Requires the agent-lsp MCP server (github.com/blackwell-systems/agent-lsp) |
| metadata | {"required-capabilities":"codeActionProvider","optional-capabilities":"documentFormattingProvider documentSymbolProvider"} |
Requires the agent-lsp MCP server.
This skill RESTRUCTURES existing code — it takes code that already exists
and moves it into a new function. This is distinct from /lsp-generate, which
creates NEW code that does not yet exist (stubs, mocks, interface implementations).
Use this skill when the code is already written; use /lsp-generate when you
need to generate code from scratch.
Invocation: User provides file_path (absolute path), start_line and
end_line (1-indexed range), and new_function_name (desired name for the
extracted function).
If LSP is not yet initialized, call mcp__lsp__start_lsp with the workspace
root first. Auto-inference applies when file paths are provided, but an explicit
start is required when switching workspaces.
Call mcp__lsp__open_document to open the file, then call
mcp__lsp__list_symbols to understand the containing function and scope:
mcp__lsp__open_document({ "file_path": "<file_path>" })
mcp__lsp__list_symbols({ "file_path": "<file_path>" })
This establishes:
new_function_name already exists in the file (name collision check)Mandatory name collision check: If new_function_name already exists as a
symbol in the document symbols list, report the conflict and stop immediately:
Cannot extract: function
new_function_namealready exists in this file. Choose a different name and retry.
Call mcp__lsp__get_server_capabilities to understand what the language server
supports:
mcp__lsp__get_server_capabilities({})
Check for codeActionProvider in the response. Note whether execute_command
is listed in executeCommandProvider.commands. This determines whether the
primary path (Step 3) is available.
Call mcp__lsp__suggest_fixes with the selection range:
mcp__lsp__suggest_fixes({
"file_path": "<file_path>",
"start_line": N,
"start_column": 1,
"end_line": M,
"end_column": 999
})
Filter the returned actions for extract-function actions: include any action
whose kind contains "refactor.extract" OR whose title contains both
"Extract" and "function" (case-insensitive).
If an extract-function action is found:
new_function_name, ask for
confirmation before proceedingmcp__lsp__execute_command if the action has a command field:
mcp__lsp__execute_command({
"command": "<action.command.command>",
"arguments": <action.command.arguments>
})
mcp__lsp__apply_edit if the action has an edit field:
mcp__lsp__apply_edit({ "workspace_edit": <action.edit> })
If no extract-function action is found: fall through to Step 4 (manual fallback).
When no code action is available, perform manual extraction:
Read the selected lines (start_line through end_line) and identify:
Build the extracted function signature based on the captured variables analysis. Display the proposed signature to the user before writing:
Proposed extraction:
func new_function_name(param1 Type1, param2 Type2) (ReturnType, error) { // selected lines }Proceed with this signature? [y/n]
Wait for user confirmation before applying any edit.
Apply edits sequentially — do NOT batch edits from different line regions into a
single apply_edit call:
First: Replace the selected lines with a call to the new function:
mcp__lsp__apply_edit({
"workspace_edit": {
"changes": {
"<file_path>": [{
"range": { "start": { "line": start_line-1, "character": 0 },
"end": { "line": end_line, "character": 0 } },
"newText": " result := new_function_name(args...)\n"
}]
}
}
})
Second: Insert the new function definition after the containing function's closing brace:
mcp__lsp__apply_edit({
"workspace_edit": {
"changes": {
"<file_path>": [{
"range": { "start": { "line": insert_line, "character": 0 },
"end": { "line": insert_line, "character": 0 } },
"newText": "\nfunc new_function_name(params) ReturnType {\n ...\n}\n"
}]
}
}
})
Apply call-site replacement first, then insert the new function. This order preserves line numbers during editing: replacing call site does not shift the insertion point for the new function definition.
After extraction via either path:
mcp__lsp__get_diagnostics({ "file_path": "<file_path>" })
If errors are reported, display them with the table of common causes below.
| Error type | Likely cause | Fix |
|---|---|---|
| Undefined variable | Captured var not passed as parameter | Add parameter |
| Type mismatch | Return type inferred incorrectly | Adjust return type in signature |
| Name shadows outer | New function name matches outer scope | Choose different name |
| Unused variable | Return value not captured at call site | Add variable at call site |
mcp__lsp__format_document({ "file_path": "<file_path>" })
This cleans up indentation introduced by the extraction.
After completing extraction, display:
## Extraction Summary
- File: path/to/file.go
- Extracted: lines N–M
- New function: new_function_name
- Path used: LSP code action / Manual fallback
- Post-extraction errors: 0
Follow with the Diagnostic Summary if any errors changed (format in references/patterns.md).