Analyze code modification propagation across dependencies with risk scores.
npx skills add https://github.com/monicajeon28/GMcruise --skill impact-analyzer
Please help me install this Agent Skill. Skill: impact-analyzer Source: https://github.com/monicajeon28/GMcruise/tree/main/.claude/skills/impact-analyzer Command: npx skills add https://github.com/monicajeon28/GMcruise --skill impact-analyzer
This Skill prevents unexpected errors and regressions by accurately predicting the direct and indirect impact of code changes. It helps developers understand the full scope of a modification, assess its risk, and identify necessary tests before implementation, ensuring safer and more confident refactoring.
utils/formatDate.ts's signature" to receive a report detailing all files that call it, their callers, the overall risk, and a list of tests to execute.Analyze the impact of deleting the function calculateTotal in src/services/order.ts.
High-intent search queries and answers about installing and using this skill.
Impact analysis traces how a code modification propagates through your codebase by identifying all direct and indirect dependents. It maps reverse dependency trees to show which files and modules are affected by changes to signatures, implementations, renames, deletions, moves, or types, giving you the full scope before refactoring.
A risk score is a numerical rating from 0–100 that assesses the potential harm of a code change based on its type and the breadth of affected code. Combined with a risk level—low, medium, high, or critical—it guides whether a change is safe to proceed with or requires additional testing and review.
Dependency analysis automatically recommends specific tests based on the impact scope of your change. By identifying all affected modules and their callers, it suggests which test suites cover the change's reach, ensuring critical areas are validated without running unnecessary tests.
Yes. Impact analysis covers renames, deletions, moves, and type changes alongside signature and implementation modifications. It traces how each kind of change propagates through direct callers and indirect dependents to reveal all code that must be updated or retested.
Direct impact is code that explicitly calls or depends on the modified function; indirect impact includes code that calls the direct dependents. Impact analysis evaluates both to show the full dependency chain, preventing cascading failures from changes you didn't anticipate.
Impact analysis requires a codebase with analyzable structure and dependency relationships. It works by building a graph of your code's connections, so no external dependencies or special setup are needed—it operates on your existing codebase structure.
bejranondaParse Python, JavaScript, and TypeScript code into ASTs for structural analysis.
hereinthehiveAnalyze downstream effects of code changes before implementation.
spallempatiEnforce mandatory peer review and automated quality gates on pull requests.
AsiaOstrichAssess project health, architecture, and risks in existing codebases.