change-impact SKILL.md skillA
change-impact from qshanx/docs-governance is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add qshanx/docs-governance/change-impact@git:20261012.bd30f6ePins git:20261012.bd30f6e in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- qshanx/docs-governance
- Path
skills/engineering/change-impact/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261012.bd30f6e, committed Oct 12, 2026
- First version recorded
- Oct 11, 2026
- Size
- 9,257 bytes
- Repository stars
- 218
- License
- MIT
在改代码、数据、接口或治理文档前做有证据的影响分析，并在实施后把计划影响与实际 diff 对照；覆盖代码调用、数据/Schema、API 契约、测试、文档、ADR、部署、迁移和回滚。用于跨模块修改、高风险变更、数据库迁移、认证、公共接口、用户问“会影响哪里”“改之前检查一下”或实施后需要反思偏差时。English triggers: change impact analysis, blast radius, pre-change analysis, migration impact, rollback plan, post-implementation alignment.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# 变更影响分析 默认只读。先用真实依赖与现有文档证明影响面，再实施；未知项明确标“未验证”。 ## 修改前 依次回答： 1. **代码**：入口、直接调用方、下游消费者、生成物和兼容层会受什么影响？ 2. **数据**：Schema、迁移、历史数据、序列化、缓存和幂等键是否变化？ 3. **接口**：API、消息、文件格式或 CLI 是否改变？消费者和提供者分别是谁？ 4. **测试**：哪些成功标准、TEST-ID、契约测试和回归命令应证明变更正确？ 5. **文档**：是否影响 MAP、ARCHITECTURE、STATUS、LOG、CONTEXT、ADR、CONTRACT、Spec/Plan、TESTS 或 REGRESSION？ 6. **发布**：部署顺序、兼容窗口、数据恢复、回滚命令和不可逆部分是什么？ 证据优先取自真实 import/调用、路由、Schema、配置、生成脚本、`git grep`、`git diff` 和可执行测试。不要凭目录名猜依赖。 ## 路由规则 - 模块职责、公共入口、依赖或状态写入变化：修改前后执行 `architecture-docs` 的“模块文档与代码边界一致性”；读取双方适用的模块入口、CONTEXT 与契约，输出约定到代码的证据和未知项。方法只在该 Skill 维护，不以本次入口文档有 diff 代替检查。 - 架构、数据库、认证、部署拓扑或长期技术策略：检查 `domain-modeling` / ADR。 - 跨端接口：先更新 `contract-first` 管理的唯一契约源，再规划消费者、提供者和联调证据。 - 需求、业务规则、风险或 Bug：让成功标准保留在 Spec/Issue，并用 `test-collaboration` 关联 TEST-ID。 - Module 行为或下游依赖变化：实施后运行 `module-regression`；若权责、状态归属、Interface、依赖方向或核心流转改变，调用 `architecture-docs` 判断必要性并维护实际架构主记录，确保 MAP 能导航；无需创建或证据不足时说明依据与缺口。 - 数据库迁移、破坏性接口、认证和生产发布：必须写回滚条件、恢复步骤、兼容期和不可逆部分；缺任何一项就标为阻塞，不代替人执行回滚。 ## 输出 小改动在回复中给出：影响对象、证据、所需验证、文档同步和未知项。只有跨模块、高风险或用户明确要求留档时，才把报告写入 `docs/impacts/`；写文件前先确认，避免制造一次性文档。 ## 按事实核对文档 解决“AI 改完功能或接口，用户还得自己找漏改文档，下一轮又被旧说明误导”的问题。候选检索由 Agent 执行并完成判读，向用户交付具体冲突、依据和处理结果，不把原始候选清单当成完成。 …
Read the whole file at its exact version.
How to install
mdr add qshanx/docs-governance/change-impact@sha256:2ebbdc4217cdf09bThe line at the top of this page pins the label git:20261012.bd30f6e, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_6n7ot2uuywaud2tc)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Oct 11, 2026 and Oct 12, 2026, more than one a day.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261012.bd30f6e latest | 2026-10-12 | bd30f6e | 9,257 B | A | view · diff |
| git:20261011.d6d08d8 | 2026-10-11 | d6d08d8 | 9,263 B | A | view · diff |
| git:20261011.856328d | 2026-10-11 | 856328d | 8,932 B | A | view · diff |
| git:20261011.d0306dc | 2026-10-11 | d0306dc | 3,264 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (9257 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
qshanx/docs-governance · 218 stars · license MIT · pushed 2026-10-16 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_6n7ot2uuywaud2tc GET https://markdownregistry.com/api/v1/resolve?ref=qshanx/docs-governance/change-impact GET https://markdownregistry.com/api/v1/blob/2ebbdc4217cdf09bbf5e38689e2b3c24c102670526f3e043d45af48664dbdb4e
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from qshanx/docs-governance
Every file in qshanx/docs-governance