菜单
Analyze the impact of changing a function. Shows callers, dependencies, and affected files. Use when user asks what happens if they change or refactor something.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
End-to-end MCP server verification — spawn stdio server, list tools, invoke each one, verify response shape.
Set up a demo session — pick a sample repo, index it, open web UI, prep the narrative.
Run full lint + format + test + frontend build. Pre-commit / pre-release check.
Cut a release — bump version, update CHANGELOG, tag, push, create GitHub release, install local binaries.
Sprint / project status from knowledge graph. Show what's planned, in-progress, done.
Audit MCP tool set — count, descriptions, consolidation candidates, budget compliance.
| name | cs-impact |
| description | Analyze the impact of changing a function. Shows callers, dependencies, and affected files. Use when user asks what happens if they change or refactor something. |
| user-invocable | true |
| argument-hint | <function-name> |
Analyze what would be affected if a function is changed.
Use the impact_analysis MCP tool with function name: $ARGUMENTS
If no arguments given, ask which function to analyze.
Show results grouped:
