agentsclimarketplace
Sign in

Change impact analysis

Skill motao123/dev-workflow-kit/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.From its SKILL.md

Install
npx -y skills add motao123/dev-workflow-kit --skill change-impact-analysis

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.0 KB, 352 tokens by cl100k_base, as published. Nobody here has run it

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

  1. Identify the proposed or in-progress change.
  2. Map directly touched files, modules, contracts, configs, and consumers.
  3. Identify likely indirect effects and regression zones.
  4. Separate must-check surfaces from lower-risk surfaces.
  5. Recommend verification focus and rollout cautions.
  6. 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 planning if scope needs to be re-sliced
  • move into the active implementation workflow for execution
  • use ship-readiness or release-rollout-strategy when 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."

What ships with it: 3 files

1.5 KB alongside SKILL.md

evals/

references/

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.