change-impact

Analyze feature or specification changes and generate an ADR-style impact report.

Updated Mar 11, 2026
One-click install
npx skills add https://github.com/t-hasuike/CLysis --skill change-impact
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: change-impact
Source: https://github.com/t-hasuike/CLysis/tree/main/legacy-analysis/skills/change-impact
Command: npx skills add https://github.com/t-hasuike/CLysis --skill change-impact

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematically assess the impact scope of feature changes and specification updates to enable informed risk assessment, planning, and smoother project collaboration.

Core Features & Use Cases

  • Static dependency tracing to identify references, call hierarchies, and potential breakpoints.
  • Dynamic dependency verification including DI bindings and configuration changes.
  • Data-flow tracing from entry points through transformations to final destinations (DB, API, etc.).
  • Risk assessment with High/Medium/Low severity and remediation planning.
  • Deliver ADR-style impact report suitable for /create-pr --plan and cross-team handoffs.

Quick Start

Provide the project context and run the impact analysis to generate an ADR-style report and remediation plan.

Frequently Asked Questions about change-impact

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I analyze the impact of API and DB schema changes in my software project?▼

Impact analysis assesses the scope of API and DB schema changes by tracing static and dynamic dependencies to identify affected components and generate a risk assessment report.

What is dependency tracing and when do I need it for feature additions?▼

Dependency tracing identifies references, call hierarchies, and configuration bindings. You need it when adding features to map potential breakpoints and assess structural risks before implementation.

How do I generate an ADR-style remediation plan for configuration updates?▼

Generate an ADR-style remediation plan by running data-flow tracing from entry points to final destinations, evaluating risks, and formatting the output for cross-team handoffs and planning.

Can I use impact analysis for cross-team handoffs and PR planning?▼

Yes, impact analysis produces an ADR-style report suitable for cross-team handoffs and directly compatible with PR planning workflows to ensure informed risk assessment and smoother collaboration.

What's the best way to assess risks when modifying software specifications?▼

Assess specification modification risks by combining static and dynamic dependency verification with data-flow analysis to classify severity as High, Medium, or Low and outline remediation steps.

Does impact analysis cover dynamic dependency verification including DI bindings?▼

Yes, impact analysis includes dynamic dependency verification to check DI bindings and configuration changes, ensuring runtime behavior is accounted for alongside static reference tracing.