Analyze blast radius before changing specific files. Use before refactoring core components, making breaking API changes, or modifying shared code to identify affected files and stakeholders.
From omen-developmentnpx claudepluginhub panbanda/omen --plugin omen-developmentThis skill uses the workspace's default tool permissions.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.
Guides implementation of event-driven hooks in Claude Code plugins using prompt-based validation and bash commands for PreToolUse, Stop, and session events.
Understand the potential blast radius of changes before making them by analyzing dependencies, coupling patterns, and ownership.
Omen CLI must be installed and available in PATH.
Run the dependency graph analysis:
omen -f json graph
Identify:
Run the temporal coupling analysis:
omen -f json temporal
Files with high temporal coupling to the target often need to change together even without explicit imports.
Run the ownership analysis:
omen -f json ownership
Identify:
Classify impact by type:
| Category | Description | Action |
|---|---|---|
| Direct | Explicit imports/calls | Will break if signature changes |
| Implicit | Temporal coupling | May break due to shared assumptions |
| Behavioral | Same owner/team | Likely understands the change |
| Unknown | No coupling, different owner | Needs extra review |
Present impact analysis as:
# Change Impact: `target/file.go:FunctionName`
## Direct Dependencies (will break)
- `consumer/a.go` - calls FunctionName directly
- `consumer/b.go` - uses returned type
- `test/target_test.go` - tests the function
## Implicit Dependencies (may break)
- `related/cache.go` - 0.85 temporal coupling
- Always changes with target
- Likely shares state or assumptions
- `related/config.go` - 0.72 temporal coupling
- Often changes together
- May depend on same configuration
## Stakeholders to Notify
- alice@example.com - Primary owner of target (85% of commits)
- bob@example.com - Owns consumer/a.go
- charlie@example.com - Owns related/cache.go
## Risk Assessment
- **Blast Radius**: 5 files directly, 12 files transitively
- **Coupling Risk**: 2 files with implicit dependencies
- **Team Impact**: 3 developers should be notified
## Recommended Approach
1. Coordinate with alice (primary owner)
2. Update tests in target_test.go first
3. Check related/cache.go for shared assumptions
4. Notify bob and charlie before merging
Strategies to minimize blast radius: