Agent skill

Change Impact

by qshanx in qshanx/docs-governance

在改代码、数据、接口或治理文档前做有证据的影响分析,并在实施后把计划影响与实际 diff 对照;覆盖代码调用、数据/Schema、API 契约、测试、文档、ADR、部署、迁移和回滚。用于跨模块修改、高风险变更、数据库迁移、认证、公共接口、用户问“会影响哪里”“改之前检查一下”或实施后需要反思偏差时。English triggers: change impact analysis, blast…

MITAuto-check passedDevelopment

Install Change Impact

skills CLI
$ npx skills add qshanx/docs-governance --skill change-impact -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install qshanx/docs-governance change-impact --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/qshanx/docs-governance.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/change-impact .claude/skills/change-impact && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
change-impact
GitHub stars
134
Token cost
~395 tokens
SKILL.md length
72 words
Files
1
Skills in repo
10
Repo updated
First seen
Licence
MIT

At a glance

在改代码、数据、接口或治理文档前做有证据的影响分析,并在实施后把计划影响与实际 diff 对照;覆盖代码调用、数据/Schema、API 契约、测试、文档、ADR、部署、迁移和回滚。用于跨模块修改、高风险变更、数据库迁移、认证、公共接口、用户问“会影响哪里”“改之前检查一下”或实施后需要反思偏差时。English triggers: change impact analysis, blast…

  • Works in 6 steps: 代码:入口、直接调用方、下游消费者、生成物和兼容层会受什么影响? → 数据:Schema、迁移、历史数据、序列化、缓存和幂等键是否变化? → 接口:API、消息、文件格式或 CLI 是否改变?消费者和提供者分别是谁? → …
  • Tasks that involve Architecture decision records
  • SKILL.md covers 修改前, 路由规则, 输出 and 实施后对照
  • Calls git

What it does

Change Impact is an agent skill from qshanx/docs-governance. 在改代码、数据、接口或治理文档前做有证据的影响分析,并在实施后把计划影响与实际 diff 对照;覆盖代码调用、数据/Schema、API 契约、测试、文档、ADR、部署、迁移和回滚。用于跨模块修改、高风险变更、数据库迁移、认证、公共接口、用户问“会影响哪里”“改之前检查一下”或实施后需要反思偏差时。English triggers: change impact analysis, blast radius, pre-change analysis, migration impact, rollback plan, post-implementation alignment.

Its SKILL.md is about 400 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Architecture decision records. The repository describes itself as: Claude Code、Codex 与 ChatGPT 的文档驱动开发治理插件:防文档腐烂、维护上下文与决策、契约协作、测试与回归证据。 The licence is MIT.

When your agent uses it

  • Tasks that involve Architecture decision records

Example prompts

  • “改之前检查一下”
  • “/change-impact”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. 代码:入口、直接调用方、下游消费者、生成物和兼容层会受什么影响?
  2. 数据:Schema、迁移、历史数据、序列化、缓存和幂等键是否变化?
  3. 接口:API、消息、文件格式或 CLI 是否改变?消费者和提供者分别是谁?
  4. 测试:哪些成功标准、TEST-ID、契约测试和回归命令应证明变更正确?
  5. 文档:是否影响 MAP、ARCHITECTURE、STATUS、LOG、CONTEXT、ADR、CONTRACT、Spec/Plan、TESTS 或 REGRESSION?
  6. 发布:部署顺序、兼容窗口、数据恢复、回滚命令和不可逆部分是什么?

What it can do on your machine

Read from SKILL.md and the folder at commit 520696e. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Change Impact loads about 395 tokens when it runs. Until then it costs about 76 tokens; SKILL.md has 72 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~76
When it runs · the whole SKILL.md, loaded when a task matches
~395

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from qshanx/docs-governance at commit 520696e, republished under its MIT licence (© qshanx). 72 words, ~395 tokens.

Download SKILL.mdSave it as .claude/skills/change-impact/SKILL.md (or your agent's skills folder).
name
change-impact
description
在改代码、数据、接口或治理文档前做有证据的影响分析,并在实施后把计划影响与实际 diff 对照;覆盖代码调用、数据/Schema、API 契约、测试、文档、ADR、部署、迁移和回滚。用于跨模块修改、高风险变更、数据库迁移、认证、公共接口、用户问“会影响哪里”“改之前检查一下”或实施后需要反思偏差时。English triggers: change impact analysis, blast radius, pre-change analysis, migration impact, rollback plan, post-implementation alignment.

变更影响分析

默认只读。先用真实依赖与现有文档证明影响面,再实施;未知项明确标“未验证”。

修改前

依次回答:

  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 和可执行测试。不要凭目录名猜依赖。

路由规则

  • 架构、数据库、认证、部署拓扑或长期技术策略:检查 context-and-decisions / ADR。
  • 跨端接口:先更新 contract-first 管理的唯一契约源,再规划消费者、提供者和联调证据。
  • 需求、业务规则、风险或 Bug:让成功标准保留在 Spec/Issue,并用 test-collaboration 关联 TEST-ID。
  • Module 行为或下游依赖变化:实施后运行 module-regression;若权责、状态归属、Interface、依赖方向或核心流转改变,同步更新 ARCHITECTURE.md,并确保 MAP 仍能导航到它。
  • 数据库迁移、破坏性接口、认证和生产发布:必须写回滚条件、恢复步骤、兼容期和不可逆部分;缺任何一项就标为阻塞,不代替人执行回滚。

输出

小改动在回复中给出:影响对象、证据、所需验证、文档同步和未知项。只有跨模块、高风险或用户明确要求留档时,才把报告写入 docs/impacts/;写文件前先确认,避免制造一次性文档。

实施后对照

完成实现后检查:

  1. 实际改动是否解决 Spec/Issue 中的原始问题。
  2. 实际 diff 是否超出已声明范围;超出项是否获得授权并补充影响分析。
  3. 测试和人工证据是否真正覆盖成功标准,而非只证明命令运行过。
  4. CONTEXT、ADR、CONTRACT、TESTS、REGRESSION、MAP、ARCHITECTURE、STATUS 和 LOG 是否按实际变化同步。
  5. 是否遗留临时代码、兼容逻辑、迁移尾项或后续 Issue。

默认在交付回复中报告对照结论。只有高风险变更或用户要求正式评审时,才保存到 docs/reviews/。不要创建通用 REFLECTION.md。

© qshanx, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/change-impact of qshanx/docs-governance.

Open the folder on GitHubat commit 520696e

Compare with similar skills

Change Impact next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Change Impact compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Change Impact this skillqshanx/docs-governance134—~395Automated safety check: PassMIT
Project Knowledgeradix-ng/primitives2741 repos~833Automated safety check: PassMIT
Requirement Tracingeclipse-ankaios/ankaios125—~2.4kAutomated safety check: PassApache-2.0
Record A Decisioninkeep/open-knowledge4.5k—~3.5kAutomated safety check: PassGPL-3.0
Coding Standardtestdouble/han281—~8.6kAutomated safety check: PassMIT
Harness Drift From Historyruvnet/ruflo74k—~632Automated safety check: NotesMIT

Similar skills

  • Project Knowledge

    radix-ng/primitives

    A skill your agent uses when you need information about this project's architecture, tech stack, coding patterns, data model, deployment setup, git workflow, or UX guidelines.

    274 GitHub starsUsed in 1 repo~833 tokens
    DevelopmentAuto-check passed
  • Requirement Tracing

    eclipse-ankaios/ankaios

    Manage requirement tracing — write new or update existing requirements/design decisions, link implementations and tests to existing ones, and maintain tracing consistency.

    125 GitHub stars~2.4k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Record A Decision

    inkeep/open-knowledge

    Records an architecture decision as a Nygard/MADR-shaped ADR under decisions/ — capturing the context that forced the choice, the options weighed, the decision itself, and its consequences in both…

    4.5k GitHub stars~3.5k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Coding Standard

    testdouble/han

    Creates and updates coding standards, conventions, rules, and guidelines for the current project.

    281 GitHub stars~8.6k tokensUpdated 9 days ago
    DevelopmentAuto-check passed
  • One-command drift detection. An agent skill from ruvnet/ruflo.

    74k GitHub stars~632 tokensUpdated today
    DevelopmentAuto-check: notes
  • Dotfile From Spec

    harperreed/dotfiles

    A skill your agent uses when you have a spec, design doc, structured plan, or promptplan and need to generate a pipeline Graphviz DOT file for headless autonomous building.

    334 GitHub stars~8.6k tokensUpdated 8 days ago
    DevelopmentAuto-check: notes

More from qshanx/docs-governance

All 10 skills in this repo
  • Agent Entrypoints

    qshanx/docs-governance

    根据项目事实与已确认讨论生成、精简或审查 AGENTS.md / CLAUDE.md,明确共享规则主文件、可执行约束、PRD / Spec 读取路标和验证入口。用于项目入口只有空模板、规范含糊、双入口冲突或需要设置 Agent 项目说明时。English triggers: AGENTS.md, CLAUDE.md, project instructions, agent entrypoint…

    134 GitHub stars~1.3k tokensUpdated today
    Auto-check passed
  • Module Regression

    qshanx/docs-governance

    大项目模块间联动回归——一份 REGRESSION.md 回归台账登记"每个模块的下游消费者 + 可执行的回归验收命令",每次改动后照台账跑回归审计,防"改一个模块悄悄弄坏其他模块"。判决靠退出码,不靠 AI 看着没问题。中文触发:模块回归、回归台账、回归审计、改A坏B、模块联动检查、影响面检查、模块牵连、下游验证、大项目改动检查。English triggers: module…

    134 GitHub stars~811 tokensUpdated today
    Auto-check passed
  • Contract First

    qshanx/docs-governance

    分前端/后端(或多个服务)多端开发的项目,用 CONTRACT.md 指向的唯一机器契约,各端只照它各做各的,防止字段漂移导致集成时白屏。支持单会话多 agent 和多终端各自跑两种模式。只要项目有前后端/多服务、接口字段老对不上、各端联调卡住、某端改了字段忘了通知别人、或前端为渲染一个页面要调一堆接口拼数据,就用这个…

    134 GitHub stars~1.2k tokensUpdated today
    Auto-check passed
  • Docs Governance

    qshanx/docs-governance

    作为面向长期 AI 协作项目的知识、决策与验证治理总入口,把优秀 Agent 的一次性工作沉淀为可继承、可验证、可持续演进的项目集体能力;根据用户意图把任务路由到活文档、领域上下文与 ADR、变更影响、接口契约、测试资产、模块回归或闭环设计能力,并在大型变更中组织正确顺序。用于用户只说“文档治理”“项目治理”“帮我整理项目知识”“改完怎么收尾”而未指定具体…

    134 GitHub stars~485 tokensUpdated today
    Auto-check passed
  • Living Docs Governance

    qshanx/docs-governance

    把长期项目的文档当成一个小系统来维护,防止文档腐烂——四份各司其职的脊柱文件(CLAUDE.md 共享章程 / CLAUDEMAP.md 地图 / PROJECTSTATUS.md 健康仪表盘 / PROJECTLOG.md 流水账)+ Codex 的 AGENTS.md 入口桥接 + 固定读序,并按需连接 ARCHITECTURE、CONTEXT、ADR、契约、测试、回归和 Issue…

    134 GitHub stars~4.1k tokensUpdated today
    Auto-check passed
  • Loop Design Check

    qshanx/docs-governance

    把一个任务"写成"一个目标导向的 loop,并"检查"这个 loop 写得对不对、会不会跑飞——防止空转烧钱 / Goodhart 作弊 / 把错的干到底。两个动作:① 写 loop(先做减法判该不该建 → 定可判定目标 → 选回路类型 → 选骨架)② 体检 loop(过五个崩法 + 可判定性 + 边界 + 降级 + judge 独立 + 判断留人红线)。中文触发:写 loop、设计…

    134 GitHub stars~1.2k tokensUpdated today
    Auto-check passed

Questions about Change Impact

What does Change Impact do?

在改代码、数据、接口或治理文档前做有证据的影响分析,并在实施后把计划影响与实际 diff 对照;覆盖代码调用、数据/Schema、API 契约、测试、文档、ADR、部署、迁移和回滚。用于跨模块修改、高风险变更、数据库迁移、认证、公共接口、用户问“会影响哪里”“改之前检查一下”或实施后需要反思偏差时。English triggers: change impact analysis, blast…. Change Impact is an agent skill from qshanx/docs-governance. 在改代码、数据、接口或治理文档前做有证据的影响分析,并在实施后把计划影响与实际 diff 对照;覆盖代码调用、数据/Schema、API 契约、测试、文档、ADR、部署、迁移和回滚。用于跨模块修改、高风险变更、数据库迁移、认证、公共接口、用户问“会影响哪里”“改之前检查一下”或实施后需要反思偏差时。English triggers: change impact analysis, blast radius, pre-change analysis, migration impact, rollback plan, post-implementation alignment.

When should I use Change Impact?

Change Impact fits situations like: tasks that involve Architecture decision records.

How do I install Change Impact in Claude Code?

Run `npx skills add qshanx/docs-governance --skill change-impact -a claude-code`. Or copy the skill folder (skills/change-impact in qshanx/docs-governance) into .claude/skills/change-impact in your project. Claude Code loads it when a task matches its description.

How do I install Change Impact in Codex?

Run `npx skills add qshanx/docs-governance --skill change-impact -a codex`. Or copy the skill folder (skills/change-impact in qshanx/docs-governance) into .agents/skills/change-impact in your project. Codex loads it when a task matches its description.

Can I use Change Impact in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add qshanx/docs-governance --skill change-impact -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/change-impact, .gemini/skills/change-impact, .github/skills/change-impact and .opencode/skills/change-impact in your project.

What does Change Impact need to run?

Going by SKILL.md and its folder, Change Impact needs the command-line tools its instructions call (git).

Does Change Impact access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Change Impact safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Change Impact use?

Change Impact is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Change Impact use?

About 395 tokens (SKILL.md is roughly 1.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Change Impact?

Skills that share tags, products or a category with Change Impact: Project Knowledge (radix-ng/primitives, 274 stars), Requirement Tracing (eclipse-ankaios/ankaios, 125 stars), Record A Decision (inkeep/open-knowledge, 4.5k stars) and Coding Standard (testdouble/han, 281 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Change Impact?

qshanx (a GitHub user) maintains it in qshanx/docs-governance, which has 134 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on October 10, 2026.

Source: qshanx/docs-governance on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.