Change impact analysis
Skill dss-time/repo-doctor-skills/plugins/repo-doctor/skills/change-impact-analysis
Bilingual cross-platform AI Skills framework|双语跨平台 AI Skills 工程框架
npx -y skills add dss-time/repo-doctor-skills --skill change-impact-analysisAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 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 author says it does
Copied from the file, not written here
Analyze general dependency and compatibility impact before modifying, renaming, moving, or deleting shared code. Use dependency-upgrade-analysis, api-contract-review, database-migration-review, or dead-code-verification when the core question is that specialized risk; do not modify files. 在修改、重命名、移动或删除共享代码前分析一般依赖关系和兼容性影响。核心问题是依赖升级、API 契约、数据库迁移或死代码可删除性时使用对应专项 Skill;本 Skill 不修改文件。
SKILL.md
2.5 KB, as published. Nobody here has run it
Change Impact Analysis(变更影响分析)
Use the section matching the user's language. 使用与用户输入语言一致的章节。
Change Impact Analysis
Use this skill before modifying, moving, renaming, deleting, or redesigning shared code.
Safety Boundary
- Analyze before editing.
- Do not modify files by default.
- Do not assume no references exist without searching.
- Treat public interfaces as compatibility-sensitive.
Workflow
- Identify the proposed change target.
- Search imports, calls, re-exports, dynamic references, route references, config usage, tests, documentation, package exports, and CI usage.
- Determine whether the target is a public interface.
- Classify blast radius and compatibility requirements.
- Identify behavior that must be preserved.
- Recommend the smallest safe change plan.
Output Format
- Change target
- Current responsibility
- References and dependencies
- Risk level
- Affected behavior
- Tests needed before changing
- Minimum safe change plan
- Unsafe actions to avoid
- Validation commands
- Final decision
变更影响分析
用于在修改、移动、重命名、删除或重新设计共享代码前分析影响范围。
安全边界
- 先分析,再修改。
- 默认不修改文件。
- 没有搜索引用前,不要假设没有调用方。
- 将公共接口视为兼容性敏感区域。
工作流程
- 识别拟变更目标。
- 搜索 import、调用、re-export、动态引用、路由引用、配置使用、测试、文档、包导出和 CI 使用。
- 判断目标是否属于公共接口。
- 评估影响范围和兼容性要求。
- 识别必须保持的行为。
- 给出最小安全修改方案。
输出格式
- 变更目标
- 当前职责
- 引用和依赖
- 风险等级
- 受影响行为
- 修改前需要的测试
- 最小安全修改方案
- 应避免的不安全操作
- 验证命令
- 最终判断