impact
Analyze system-wide impact of changes before making them. Use before modifying shared utilities, changing APIs, or refactoring core functionality.
What this skill does
# Impact Analysis Analyze the system-wide impact of proposed or recent changes before you make them. ## Philosophy Code doesn't exist in isolation. A "small fix" in a shared utility can break ten components. A type change can cascade through the entire codebase. > "What else depends on this? What might break?" This skill isn't about being cautious—it's about being **informed**. Make changes with full knowledge of their ripple effects. ## When to Use Run `/impact` before: - Modifying shared utilities or types - Changing API signatures - Refactoring core functionality - Deleting or renaming exports - Making changes that "seem small but might ripple" ## Input The user will provide: - File path(s) being changed, OR - Function/class/type name being modified, OR - Description of planned change If nothing provided, analyze uncommitted changes. ## Process ### 1. Identify Change Scope Determine what's being modified: - File(s) affected - Exports being changed (functions, types, classes) - API signatures being modified - Data structures being altered ### 2. Find Direct Dependents Search for code that directly uses the modified code: - Files that import from the changed file - Functions/components that call the modified code - Types that extend or reference modified types ### 3. Check Test Coverage Find related tests: - Unit tests for the modified code - Integration tests that exercise this path - Tests that might need updating ### 4. Trace Downstream Effects Follow the impact chain: - Direct dependents → their dependents - API routes that expose this functionality - UI components that consume this data ## Output Format Keep it **compact**. Tables for findings, clear risk assessment. ```markdown ## Impact Analysis: [Change Description] **Scope**: [What's being changed] **Risk Level**: Low | Medium | High --- ### Direct Dependents | File | Usage | Risk | |------|-------|------| | `consumer.ts:45` | Calls `modifiedFunction()` | Medium | | `component.tsx:23` | Uses `ModifiedType` | Low | ### Test Coverage **Tests found:** - `__tests__/file.test.ts` - Direct unit tests ✓ **Tests that may need updates:** - `integration/flow.test.ts` - Uses affected flow ### Breaking Change Assessment | Check | Status | |-------|--------| | Public API changes | Yes / No | | Type signature changes | Yes / No | | Behavioral changes | Yes / No | | Database/schema changes | Yes / No | --- ### Recommendations 1. **Before changing**: [Specific prep work] 2. **Update alongside**: [Files that need coordinated changes] 3. **Tests to run**: [Specific test commands] 4. **Communicate to**: [Teams or people who should know] ### Summary [1-2 sentences: X dependents found, Y tests affected, overall risk level and why] ``` ## Why This Matters Impact analysis prevents: - **Surprise breakages** in unrelated parts of the codebase - **Incomplete migrations** where some consumers are missed - **Test failures** that could have been anticipated - **Team friction** when changes affect others' work The five minutes spent on impact analysis saves hours of debugging and rollbacks.
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.