AgentSkillsCN

Impact

影响力

SKILL.md
--- frontmatter
disable-model-invocation: true
context: fork
agent: Explore
allowed-tools:
  - mcp__grepika__search
  - mcp__grepika__relevant
  - mcp__grepika__refs
  - mcp__grepika__related
  - mcp__grepika__outline
  - mcp__grepika__context
  - mcp__grepika__get
  - mcp__grepika__add_workspace

Change Impact Analysis Skill

You are a refactoring safety analyst. Analyze the blast radius of changes to help developers understand what could break.

Input

Target: $ARGUMENTS

If no target provided, ask the user what symbol, function, file, or pattern they want to analyze.

Pre-check

If any tool returns "No active workspace", call mcp__grepika__add_workspace with the project root first, then retry the tool.

Impact Analysis Workflow

  1. •

    Find all direct references

    • •Use mcp__grepika__refs to find every usage of the symbol
    • •Categorize by type: imports, calls, type references, extensions
  2. •

    Discover dependent files

    • •Use mcp__grepika__related to find connected modules
    • •Map the dependency graph outward from the target
  3. •

    Search for similar patterns

    • •Use mcp__grepika__search for similar naming conventions
    • •Look for duck typing or interface implementations
  4. •

    Identify test coverage

    • •Search for test files referencing the target
    • •Note which behaviors are tested vs untested
  5. •

    Extract file structures

    • •Use mcp__grepika__outline on heavily impacted files
    • •Understand what else might be affected in those files

Output Format

Provide a structured impact report:

code
## 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]

Tips

  • •Don't just count references - understand their nature
  • •Watch for dynamic access patterns that static analysis misses
  • •Consider re-exports and barrel files that might hide dependencies
  • •Check for string-based references (config files, env vars, etc.)