verify-change

Name: verify-change
Availability: InStock
Author: wzyxdwll

Analyze code and documentation changes to identify gaps and sync issues.

14|1|Updated May 6, 2026

Search Tags:#automation #quality-gate #code-review #tests #git-diff #doc-sync #change-analysis

Ready to run

npx skills add https://github.com/wzyxdwll/ccgx-workflow --skill verify-change-wzyxdwll

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verify-change
Source: https://github.com/wzyxdwll/ccgx-workflow/tree/main/templates/skills/tools/verify-change
Command: npx skills add https://github.com/wzyxdwll/ccgx-workflow --skill verify-change-wzyxdwll

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Automates the detection of gaps between code changes and documentation, enabling teams to maintain accurate docs and tests during iterative development.

Core Features & Use Cases

Automated change analysis across code and docs to surface misalignments.
Doc-sync checks that flag missing or outdated documentation relative to changes.
Impact assessment and reporting to guide reviews, testing, and releases.
CLI support for staged, working, or committed changes to fit various workflows.
Use Case: during PR reviews or before merges to ensure documentation and tests match code changes.

Quick Start

Run the analyzer from the skill directory to scan changes and generate a report.

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 synced with documentation?▼

To check if code changes are synced with documentation, you can run an automated change analysis tool that detects misalignments between code updates and docs, flagging missing or outdated documentation relative to your latest commits.

What is a revision-loop gate for code review?▼

A revision-loop gate is an automated quality check that enforces thresholds for change convergence during code review, ensuring iterative changes meet stability criteria before approvals and merges are granted.

How do I analyze git diff for missing tests and configuration changes?▼

You can analyze git diff for missing tests by applying an automated change analyzer to your working, staged, or committed changes, which highlights missing tests and configuration updates to guide reviews and testing.

Can I run a doc-sync check on staged changes before a merge?▼

Yes, you can run a doc-sync check on staged changes before a merge. The analysis supports staged, working, or committed changes to fit various development workflows and ensure documentation matches code updates.

Does automated change analysis work without additional dependencies?▼

Yes, automated change analysis works without additional dependencies. The skill operates independently using its built-in scripts to assess impact and generate synchronization reports for your codebase.