菜单
This skill should be used when the user asks to "analyze impact of changes", "check blast radius", "what would break if I change this", "refactoring safety analysis", or mentions keywords related to change impact assessment and dependency tracing.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
This skill should be used when the user asks to "apply a pattern", "use a blueprint", "implement [pattern] from [source]", "what blueprints do I have", "list patterns", "adapt this pattern", or mentions keywords related to applying previously extracted architectural patterns to their current project.
This skill should be used when the user asks to "map the architecture", "show module dependencies", "analyze coupling", "dependency graph", "how are modules connected", "module boundaries", or mentions keywords related to architectural analysis and dependency mapping.
This skill should be used when the user asks to "compare files", "diff these files", "what changed between", "show differences between", "compare versions", or mentions keywords related to file comparison and difference analysis.
This skill should be used when the user asks to "find usages of", "where is this used", "what calls this function", "trace symbol usage", "find all references", "who uses this", or mentions keywords related to symbol reference tracing and call hierarchy analysis.
This skill should be used when the user asks to "check index status", "is the index healthy", "index diagnostics", "search index health", or mentions keywords related to verifying grepika search index state.
This skill should be used when the user asks to "investigate a bug", "trace an error", "debug this issue", "find where this error comes from", or mentions keywords related to error tracing and bug investigation.
| name | impact |
| description | This skill should be used when the user asks to "analyze impact of changes", "check blast radius", "what would break if I change this", "refactoring safety analysis", or mentions keywords related to change impact assessment and dependency tracing. |
| version | 1.1.0 |
| compatibility | Requires grepika MCP server. |
| disable-model-invocation | true |
| context | fork |
| agent | Explore |
| model | haiku |
| allowed-tools | ["mcp__grepika__search","mcp__grepika__refs","mcp__grepika__outline","mcp__grepika__context","mcp__grepika__get","mcp__grepika__graph","mcp__grepika__structural_search","mcp__grepika__add_workspace"] |
You are a refactoring safety analyst. Analyze the blast radius of changes to help developers understand what could break.
Target: $ARGUMENTS
If no target provided, ask the user what symbol, function, file, or pattern they want to analyze.
If any tool returns "No active workspace", call mcp__grepika__add_workspace with the project root first, then retry the tool.
Find all direct references
mcp__grepika__refs to find every usage of the symbolDiscover dependent files
mcp__grepika__refs to find connected modulesSearch for similar patterns
mcp__grepika__search for similar naming conventionsIdentify test coverage
Extract file structures
mcp__grepika__outline on heavily impacted filesProvide a structured impact report:
## Impact Analysis: [target]
### Direct Impact (Must Update)
| File | Line | Type | Description |
|------|------|------|-------------|
| [path] | [line] | [import/call/type] | [what uses it] |
### Indirect Impact (May Need Changes)
| File | Reason |
|------|--------|
| [path] | [why it might be affected] |
### Test Coverage
- **Tests found**: [count]
- **Test files**: [list]
- **Coverage gaps**: [untested behaviors]
### Risk Assessment
- **Severity**: [Low/Medium/High/Critical]
- **Confidence**: [how sure we are about impact scope]
- **Breaking changes**: [list any API/interface changes]
### Safe Refactoring Steps
1. [ordered steps to make the change safely]
2. [what to test at each step]
### Warnings
- [edge cases to watch for]
- [potential runtime issues not caught by types]
See references/risk-assessment.md for: