impact-flow

Features and purpose

Codebase flow analysis for dependency visualization, impact assessment, and health scoring. Use PROACTIVELY when users need: (1) Dependency/import analysis ("what imports this?", "dependency graph", "module relationships") (2) Blast radius/impact analysis ("if I change X", "what's affected", "impact of modifying") (3) Code health scoring ("codebase health", "health grade", "technical debt score") (4) Execution flow tracing ("trace through", "call path", "how does data flow") (5) Dead code detection ("unused exports", "safe to delete", "orphan code") (6) Comprehensive analysis ("full analysis", "analyze this codebase") Triggers: "impact-flow", "impact flow", "dependency graph", "blast radius", "impact analysis", "health score", "what depends on", "call graph", "trace execution", "dead code", "module dependencies" NOTE: For security scanning, defer to security-sentinel. For design patterns, defer to pattern-recognition-specialist. For architecture compliance, defer to architecture-strategist.

Quick start

Follow the repository instructions for this skill and your agent. Review the files and dependencies before adding it to your workflow.