Change Impact Analysis
Use when the main question is what a proposed or partial change will affect across code, interfaces, configs, tests, docs, consumers, and rollout surfaces. This skill maps blast radius before implementation, merge, or release.
Install
$ agentstack add skill-motao123-dev-workflow-kit-change-impact-analysis ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-motao123-dev-workflow-kit-change-impact-analysis) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Change Impact Analysis
Use this skill when the key uncertainty is breadth of impact rather than how to write the code.
Trigger Conditions
Use this skill when:
- a change may affect multiple modules, consumers, or environments
- the team needs to know what else must be updated before implementation
- API, schema, config, docs, tests, or rollout surfaces may be touched indirectly
- the user asks what could break if a change goes in
- release risk depends on understanding downstream effects first
Do not use this skill for root-cause debugging or for deciding the internal structure of a refactor.
Workflow
- Identify the proposed or in-progress change.
- Map directly touched files, modules, contracts, configs, and consumers.
- Identify likely indirect effects and regression zones.
- Separate must-check surfaces from lower-risk surfaces.
- Recommend verification focus and rollout cautions.
- Hand off to the next workflow step.
Output
For non-trivial work, provide:
- impacted surfaces
- direct vs indirect consequences
- likely regression zones
- verification focus areas
- rollout or migration cautions
- recommended next action
Coordination
After impact analysis:
- use
planningif scope needs to be re-sliced - move into the active implementation workflow for execution
- use
ship-readinessorrelease-rollout-strategywhen impact affects release shape
Invocation Examples
- "Use change-impact-analysis to show what else this schema change could affect."
- "Use change-impact-analysis before implementation so we know which tests, docs, and clients are in scope."
- "Use change-impact-analysis to identify the likely regression zones for this config change."
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: motao123
- Source: motao123/dev-workflow-kit
- License: MIT
- Homepage: https://motao123.github.io/dev-workflow-kit/
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.