agentleFS
dss-timedss-time/repo-doctor-skills/skills/change-impact-analysis/SKILL.md

change-impact-analysis

Skill1 starsChanged 4 months agoMITView on GitHub

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 不修改文件。

We split this skill into the rules it gives an agent

6 rules. 0 are common, 5 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Default to fast; bounded natural-language invocation is allowed.

    line 10
  2. Distinctive:

    Use this skill before modifying, moving, renaming, deleting, or redesigning shared code.

    line 17
  3. Distinctive:

    Do not modify files by default.

    line 22
  4. Distinctive:

    Do not assume no references exist without searching.

    line 23
  5. Distinctive:

    Treat public interfaces as compatibility-sensitive.

    line 24
  6. Distinctive:

    Search imports, calls, re-exports, dynamic references, route references, config usage, tests, documentation, package exports, and CI usage.

    line 29

“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

English

Execution Contract

Default to fast; bounded natural-language invocation is allowed. Complete one primary task by default. Continue an authorized end-to-end workflow within each Skill's permissions; Router remains recommendation-only. Pause for new material decisions or scope, not authorization already given. For a human-only blocker, give location, action, success signal and resume step; never request secret values or assume completion. Validate according to actual risk; security, production, migrations, releases and other high-risk work use audit. Read references/execution-modes.en.md only when mode selection is unclear.

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

  1. Identify the proposed change target.
  2. Search imports, calls, re-exports, dynamic references, route references, config usage, tests, documentation, package exports, and CI usage.
  3. Determine whether the target is a public interface.
  4. Classify blast radius and compatibility requirements.
  5. Identify behavior that must be preserved.
  6. Recommend the smallest safe change plan.

Output Format

  1. Change target
  2. Current responsibility
  3. References and dependencies
  4. Risk level
  5. Affected behavior
  6. Tests needed before changing
  7. Minimum safe change plan
  8. Unsafe actions to avoid
  9. Validation commands
  10. Final decision

简体中文

执行契约

默认使用 fast;允许边界明确的自然语言隐式调用。 默认完成一个主任务。用户已授权完整流程时,在各 Skill 权限内连续完成;Router 仍只推荐。新重大决策或超出授权时暂停,不重复索取已有授权。 必须由用户完成的阻塞步骤:给出操作位置、具体动作、成功标志、恢复步骤;不要求粘贴秘密值,不代替用户确认完成。 按实际风险选择验证;安全、生产、迁移、发布等高风险工作使用 audit。模式不明确时才读取 references/execution-modes.zh-CN.md。

变更影响分析

用于在修改、移动、重命名、删除或重新设计共享代码前分析影响范围。

安全边界

  • 先分析,再修改。
  • 默认不修改文件。
  • 没有搜索引用前,不要假设没有调用方。
  • 将公共接口视为兼容性敏感区域。

工作流程

  1. 识别拟变更目标。
  2. 搜索 import、调用、re-export、动态引用、路由引用、配置使用、测试、文档、包导出和 CI 使用。
  3. 判断目标是否属于公共接口。
  4. 评估影响范围和兼容性要求。
  5. 识别必须保持的行为。
  6. 给出最小安全修改方案。

输出格式

  1. 变更目标
  2. 当前职责
  3. 引用和依赖
  4. 风险等级
  5. 受影响行为
  6. 修改前需要的测试
  7. 最小安全修改方案
  8. 应避免的不安全操作
  9. 验证命令
  10. 最终判断

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.