change-guard

Analyze ripple effects and enforce documentation updates before code commits.

Updated Mar 23, 2026
One-click install
npx skills add https://github.com/0xEdenY/eden-claude-skills --skill change-guard
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: change-guard
Source: https://github.com/0xEdenY/eden-claude-skills/tree/main/change-guard
Command: npx skills add https://github.com/0xEdenY/eden-claude-skills --skill change-guard

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

变更守卫(影响分析→完整性检查→文档同步)。当用户说"改一下这个功能"、"重构"、"修 bug"、"改了 X 但 Y 好像也要改"、"检查一下文档"时触发。

Core Features & Use Cases

提供四个工作流来系统性地解决变更中的牵一发而动全身的问题:

  • 变更前:影响分析,开始改代码之前分析这次变更会影响哪些文件和模块
  • 变更后:完整性检查,改完代码、commit 之前检查是否遗漏了关联更新
  • 出问题:系统性排查,代码出了 bug 时从症状出发定位根因
  • 定期:文档同步,每完成 3-5 个 Task 或每轮迭代后,确保 docs/ 目录和代码一致

Quick Start

在开始变更前,使用本 Skill 的变更前影响分析工作流来界定变更范围并输出影响清单。

Frequently Asked Questions about change-guard

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I analyze the ripple effects of code changes before committing?

Pre-change impact analysis maps ripple effects across files and modules before code edits. It generates a structured influence manifest and cross-file impact tracking list to define the full scope of required modifications.

How do I check for missed dependency updates after refactoring?

Post-change integrity checks verify dependency updates after refactoring. It cross-references modified code against related modules to identify and flag any missed updates before a commit.

What is the best way to trace systemic bugs back to their root cause?

Systemic bug investigation traces symptoms back to their root cause. It follows cross-file influence paths through the codebase to isolate the exact origin of the failure.

How do I synchronize project documentation with source code changes?

Documentation synchronization enforces mandatory doc updates before commits. It periodically checks the docs directory against code changes to keep project documentation aligned after iterations.

When should I use an automated change impact analysis workflow?

Automated change impact analysis is used when modifying features, refactoring, or fixing bugs. It enforces structured risk-aware planning to prevent overlooked dependencies in complex workflows.