skills.rest
FlyFission
FlyFissionCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

checking-what-a-change-affects

Generate a change-impact.md with actions, blockers, and owners for ripple effects.

33|Updated May 24, 2026
Search Tags:#governance#evidence#traceability#risk-management#change-impact#release-readiness#ripple
One-click install
npx skills add https://github.com/FlyFission/nuclear-grade-context-engineering --skill checking-what-a-change-affects
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: checking-what-a-change-affects
Source: https://github.com/FlyFission/nuclear-grade-context-engineering/tree/main/skills/checking-what-a-change-affects
Command: npx skills add https://github.com/FlyFission/nuclear-grade-context-engineering --skill checking-what-a-change-affects

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Screen ripple effects when a controlled change could leave docs, tests, skills, commands, templates, checkers, prompts, releases, saved versions, or runtime schema/state out of date, and identify triggers to re-check.

Core Features & Use Cases

  • Detect ripple effects across artifact families when a change occurs.
  • Produce actionable change-impact artifacts like risk, basis, plan, and diff with owners and follow-ups.
  • Integrate with release posture to carry blockers or decisions into ship.

Quick Start

Run a ripple-effect check across the controlled items list to surface stale surfaces, assign actions, and produce change-impact artifacts.

Frequently Asked Questions about checking-what-a-change-affects

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

FAQPage Schema
How do I check the ripple effects of a code change across docs, tests, and templates?▼

To check change impact ripple effects, screen controlled changes against artifact families like docs, tests, skills, and templates to identify stale surfaces, assign per-item actions, and generate a change-impact.md with owners and follow-ups.

What is change impact analysis in software engineering?▼

Change impact analysis identifies the ripple effects when a controlled change leaves runtime contracts, saved versions, or releases out of date, producing actionable artifacts that link evidence and plan next release steps.

How do I track release readiness and blockers after modifying runtime schemas?▼

Track release readiness by screening the modified runtime blast radius to surface stale surfaces, generating a change-impact.md that carries blockers, re-check triggers, and decisions into the ship posture.

How do I assign owners and follow-up actions for outdated artifacts after a release?▼

Assign owners by running a ripple-effect check across controlled items to produce change-impact artifacts, linking evidence and explicitly defining per-item actions and follow-up triggers for each outdated surface.

When do I need to perform a change impact assessment for governance and traceability?▼

Perform a change impact assessment when changes touch multiple artifact families, runtime blast radius, or public claims, requiring explicit actions, evidence, and traceability to keep releases and runtime contracts updated.

Related Skills

Explore More Software Engineering Skills→
MykhailoDmytriakhaMykhailoDmytriakha

30-analyze-impact-150

Map upstream dependencies, downstream impact, and blast radius of system changes.

Community
Advanced
remiboivin021remiboivin021

release

Evaluate feature branches against acceptance criteria and output a MERGE READY or NOT READY verdict.

Community
Advanced
vTRKAvTRKA

pre-pr-check

Verify pull request diffs against intent and produce evidence bundles.

Community
Advanced
raydocsraydocs

flow-gap-analyst

Identify gaps, edge cases, and questions in feature specs.

Community
Advanced