用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt;运行前请先检查来源。
npx skills add https://github.com/kubernetes-sigs/kueue --skill extract-helpers命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地?可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
基于 SOC 职业分类
| name | extract-helpers |
| description | Review that local variables with unnecessarily wide scope are extracted into helper functions. |
| license | Apache-2.0 |
| metadata | {"copyright":"The Kubernetes Authors"} |
Flag: A local variable whose scope spans more of a function than it needs to — it's only used inside a self-contained block of logic.
Ask: Extract that block into a helper function. This limits the variable's lifetime to the helper, shortens the enclosing function, and makes the intent clearer.
func Greeting(user User) string {
name := strings.TrimSpace(user.FirstName)
if name == "" {
name = "friend"
}
name = strings.Title(name)
return fmt.Sprintf("Hello, %s! You have %d new messages.", name, user.Unread)
}
name is built up over three lines, then used once. Its scope spans the whole function for no reason. Real code tends to have more extreme versions of this.
vs.
func displayName(user User) string {
name := strings.TrimSpace(user.FirstName)
if name == "" {
return "friend"
}
return strings.Title(name)
}
func Greeting(user User) string {
return fmt.Sprintf("Hello, %s! You have %d new messages.", displayName(user), user.Unread)
}
name now lives only inside displayName, and Greeting is a single expressive line.