verify-change

Analyze Git changes for documentation sync and test coverage.

5.8k|441|Updated Jan 4, 2026
One-click install
npx skills add https://github.com/fengshao1227/ccg-workflow --skill verify-change
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify-change
Source: https://github.com/fengshao1227/ccg-workflow/tree/main/templates/skills/tools/verify-change
Command: npx skills add https://github.com/fengshao1227/ccg-workflow --skill verify-change

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires child_process, path, fs, and includes scripts (resource) components.

What problem does it solve?

This Skill ensures that code changes are accompanied by corresponding documentation updates and that the overall impact of a change is well-understood before it's committed.

Core Features & Use Cases

  • Code-Doc Sync Check: Detects if documentation (like README.md or DESIGN.md) has been updated when code changes.
  • Impact Assessment: Evaluates the scope of changes, including lines of code modified, and checks for associated test updates.
  • Use Case: Before committing a significant refactor, this Skill can automatically flag if the design document hasn't been updated to reflect the new architecture, preventing knowledge gaps.

Quick Start

Run the change analyzer script to check your current working directory changes.

Frequently Asked Questions about verify-change

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

FAQPage Schema
How do I check if my code changes are in sync with documentation before committing?

To check code-doc sync before committing, analyze working, staged, or committed Git changes to detect if README.md and DESIGN.md have been updated. This ensures documentation accurately reflects the latest architectural state.

What is impact analysis for code modifications in Git?

Impact analysis for Git code modifications evaluates change scope by identifying affected modules, calculating modified lines of code, and checking for associated test updates to assess overall change severity.

Can I run a documentation sync check on staged changes in Git?

Yes, you can run a documentation sync check on staged changes in Git. The analysis operates on working, staged, and committed changes to detect if README.md or DESIGN.md requires corresponding updates.

Does this code review tool evaluate test coverage against code alterations?

Yes, this code review tool evaluates test coverage against code alterations. It assesses the impact of changes by checking for associated test updates and identifying affected modules before a Git commit.

What is the best way to prevent knowledge gaps during a major code refactor?

The best way to prevent knowledge gaps during a major refactor is to automatically flag missing design document updates. Analyze code modifications to ensure DESIGN.md reflects the new architecture before committing.

When do I need a commit pre-check for documentation synchronization?

You need a commit pre-check for documentation synchronization when modifying code logic that impacts existing architecture. It detects outdated README.md or DESIGN.md files and evaluates test coverage before changes are committed.