Stats
Actions
Tags
From omni-link-hustlexp
Analyze the cross-repo impact of uncommitted changes. Shows ripple effects across all configured repositories.
How this command is triggered — by the user, by Claude, or both
Slash command
/omni-link-hustlexp:impactThe summary Claude sees in its command listing — used to decide when to auto-load this command
# /impact — Cross-Repo Impact Analysis Analyze the impact of uncommitted changes across the entire ecosystem. Detects which files have changed, traces their effects through API bridges, type lineage, and dependency chains, and reports what will be affected. ## Execution Run the omni-link CLI impact command: Config auto-detection follows the same order as `/scan`. ## Output Display the impact report as a ripple analysis: For each impact path found: ### Summary After listing all impact paths: - **Total triggers**: Number of changed files detected - **Total affected**: Number of ...
Analyze the impact of uncommitted changes across the entire ecosystem. Detects which files have changed, traces their effects through API bridges, type lineage, and dependency chains, and reports what will be affected.
Run the omni-link CLI impact command:
omni-link impact --config <auto-detect>
Config auto-detection follows the same order as /scan.
Display the impact report as a ripple analysis:
For each impact path found:
Trigger: [repo]/[file] — [change description]
Affected:
1. [repo]/[file]:[line] — [reason] — severity: [BREAKING/warning/info]
2. [repo]/[file]:[line] — [reason] — severity: [BREAKING/warning/info]
After listing all impact paths:
If no uncommitted changes are detected or no cross-repo impact exists:
No cross-repo impact detected. All uncommitted changes are contained within their respective repos.
If BREAKING items are found, recommend:
ecosystem-planner skillupgrade-executor skillnpx claudepluginhub sebdysart/omni-link-hustlexp --plugin omni-link-hustlexp/impactPerforms cascade impact analysis on a file by reading module docstrings to show dependency chain of callers up to 3 levels, with exports, rules, and summary.
/impactFans out parallel agents to map the blast radius of a file, function, or directory before making changes — imports, tests, CI pipelines, docs, and code owners.