{"skill":{"slug":"bookforge-change-effect-analysis","displayName":"Change Effect Analysis","summary":"Trace the blast radius of a legacy code change and produce a test placement plan with pinch points. Use whenever a developer needs to decide WHERE to write t...","tags":{"bookforge":"1.0.0","impact-analysis":"1.0.0","latest":"1.0.0","legacy-code":"1.0.0","refactoring":"1.0.0","software-engineering":"1.0.0","testing":"1.0.0"},"stats":{"comments":0,"downloads":16,"installsAllTime":0,"installsCurrent":0,"stars":0,"versions":1},"createdAt":1777466766230,"updatedAt":1777468608241},"latestVersion":{"version":"1.0.0","createdAt":1777466766230,"changelog":"- Initial release of the skill \"change-effect-analysis\" for software engineers working with legacy code.\n- Provides a systematic process to identify the ripple effects (\"blast radius\") of a proposed code change.\n- Produces a focused test placement plan by identifying high-leverage test \"pinch points.\"\n- Supports use cases where changes affect multiple classes or have complex propagation.\n- Designed to be language-agnostic and useful even where existing tests are missing.\n- Requires identification of the change point, change description, and access to the codebase.","license":"MIT-0"},"metadata":{"os":null,"systems":null},"owner":{"handle":"quochungto","userId":"s176b6gfk8djgcz320d83ta4e184bx1v","displayName":"Hung Quoc To","image":"https://avatars.githubusercontent.com/u/88069966?v=4"},"moderation":null}