change-impact
From the author
在改代码、数据、接口或治理文档前做有证据的影响分析，并在实施后把计划影响与实际 diff 对照；覆盖代码调用、数据/Schema、API 契约、测试、文档、ADR、部署、迁移和回滚。用于跨模块修改、高风险变更、数据库迁移、认证、公共接口、用户问“会影响哪里”“改之前检查一下”或实施后需要反思偏差时。English triggers: change impact analysis, blast radius, pre-change analysis, migration impact, rollback plan, post-implementation alignment.
Install
npx skills add qshanx/docs-governance --skill change-impact -a claude-code
Installs to .claude/skills/change-impact/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 85
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- codexqa-change-analysisopenqa-cn/codexqaChange-impact analysis for one diff: use CodexQA diff indexing (`index --diff-base` tags nodes and files `add` / `change` / `delete`, then `change-groups` / `symbol-diff` / `file-base`) to write one HTML report (affected entries, changed methods, test plan, coverage verdict, sensitive paths) and add runnable test files in the analyzed repo for uncovered points (add only; do not edit existing test files). Use when the user mentions change impact, change analysis, blast radius, affected entries, added methods, changed methods, test plan, generate or recall tests, link existing tests, entry points, 变更分析, 变更代码分析, 影响面, 影响入口, 测试方案, or 召回测试用例. Requires the codexqa CLI. One change only. Whole-repo analysis with no diff, and general symbol-graph Q&A, are codexqa-code-analyzer, not this skill. Former skill name: change-impact-analysis.Testing★ 234
- blast-radiusmichael-denyer/pstack-claudeFind what a change could break somewhere else before it ships, beyond the diff, and prove the one fact it's safe because of by running real code instead of writing it up. Use for 'blast radius of X', 'what could this break', reviewing a small diff you don't trust, or a brief that asserts something about existing code ('make X public', 'X already handles Y') before you design against that assertion.Design★ 3.4K
- change-requestanthropics/knowledge-work-pluginsCreate a change management request with impact analysis and rollback plan. Use when proposing a system or process change that needs approval, preparing a change record for CAB review, documenting risk and rollback steps before a deployment, or planning stakeholder communications for a rollout.OfficialDevOps★ 32.5K
- Test Impact AnalysisPramodDutta/qaskillsAnalyzing code changes to determine which tests are impacted, enabling selective test execution and faster CI feedback loops.Testing★ 240
- what-breakssuboss87/FDEOpsAssess the impact of a proposed change on dependencies and shared infrastructure. Use before touching unfamiliar or consequential systems.DevOps★ 941
- reviewdzhng/skillsCloseout pass on a finished substantive change — sequence refactor-clean (shape), code-review (diff), and write-docs (docs) so all three run, in the order where each feeds the next. Use after implementing a slice or feature and before calling it done or committing; when the user asks for a final review, a cleanup-and-document pass, or to "review everything." For a diff-only audit, reach code-review directly.Engineering★ 1.4K
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in