change-impact-analysis
Skill1 starsChanged 4 months agoNo licenceView on GitHub
Perform deployment-phase Change Impact Analysis for any repository. Given changed files (or auto-detected via git), builds a directed dependency graph, reverse-BFS traverses it to find every directly and transitively affected module, validates API contracts (OpenAPI/GraphQL/Protobuf) for breaking changes, maps files to CODEOWNERS, and computes a deterministic 0-100 deployment risk score (LOW/MEDIUM/ HIGH/CRITICAL). Produces an Impact Report, machine-readable JSON, and a Deployment Checklist. Trigger on: change impact analysis, analyse/analyze this PR, what is affected by this change, deployment risk, blast radius, what tests are needed, who owns this code, is it safe to deploy, breaking changes, impacted APIs, regression areas, or a list of changed files with "what will break". No API key required.
6 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- wannanbigpig/ai-engineering-collaborationtheir own version, first seen Nov 6, 2026
- dss-time/repo-doctor-skillstheir own version, first seen Oct 15, 2026
- fzfclee/consulting-skillstheir own version, first seen Oct 13, 2026
- motao123/dev-workflow-kittheir own version, first seen Jun 13, 2026
- sarveshtalele/mcp-skills-registryedited, first seen Jun 12, 2026
- jdm4pku/RE-Skillstheir own version, first seen Apr 5, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- sarveshtalele/mcp-skills-registry★ 278% same
Wrote their own version · 5
- jdm4pku/RE-Skills★ 26same name
- fzfclee/consulting-skills★ 6same name
- wannanbigpig/ai-engineering-collaboration★ 2same name
- dss-time/repo-doctor-skills★ 1same name
- motao123/dev-workflow-kit★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository2 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- change-impact-analysisSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
16 rules. 0 are common, 9 are distinctive, and 7 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
9
Distinctive
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

