skills.rest
telagod
telagodCOMMUNITY
Explore all skills by this author →
GitHub

verify-change

Analyze workspace changes to detect documentation drift and missing tests.

238|30|Updated Feb 2, 2026
Search Tags:#git#testing#documentation#code-review#analyze#changes
One-click install
npx skills add https://github.com/telagod/code-abyss --skill verify-change-telagod
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verify-change
Source: https://github.com/telagod/code-abyss/tree/main/skills/tools/verify-change
Command: npx skills add https://github.com/telagod/code-abyss --skill verify-change-telagod

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Tracking and validating changes across code, docs, and configuration is error-prone. This skill provides automated analysis to ensure documentation remains in sync with code, tests are updated when changes occur, and potential risks are surfaced before merge.

Core Features & Use Cases

  • Automatic change analysis across code, docs, tests, and configuration.
  • Detects drift between code changes and documentation, flags missing README or DESIGN updates.
  • Impact assessment and reporting to guide reviews and approvals.
  • Use Case: during a PR, run the analyzer to catch untested changes and missing documentation updates.

Quick Start

Analyze the current workspace changes by running the change_analyzer.js script to produce 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 detect documentation drift and missing tests before a git commit?▼

To detect documentation drift and missing tests before a git commit, you can analyze workspace changes to evaluate synchronization across code, docs, and configuration. This surfaces untested changes and flags missing updates to guide code reviews.

How do I check if documentation is synchronized with code changes in a pull request?▼

Checking documentation synchronization in a pull request involves analyzing workspace changes to identify discrepancies between code and docs. It automatically flags missing README or DESIGN updates to ensure documentation remains in sync with code modifications.

What is automated change analysis for code reviews?▼

Automated change analysis for code reviews is the process of evaluating workspace changes across code, docs, tests, and configuration. It identifies drift, assesses impact, and enforces checks for test coverage and configuration updates to guide approvals.

Can I run a change analyzer script to catch missing configuration updates in a release workflow?▼

Yes, you can run a change analyzer script to catch missing configuration updates in a release workflow. The script analyzes workspace changes and enforces checks to surface potential risks and configuration drift before merging.

Does the change analysis work without external dependencies?▼

Yes, the change analysis works without external dependencies. It relies on internal scripts to automatically analyze workspace changes, identify code and doc modifications, and evaluate synchronization for pre-commit checks and pull requests.

Related Skills

Explore More Software Engineering Skills→
n-marusovn-marusov

aif-qa

Automate QA by generating change summaries, test plans, and test cases.

Community
Advanced
Envy-7zEnvy-7z

mobile-pr-merge-gatekeeper

Analyze Android and Flutter pull request diffs and classify findings by severity.

Community
Advanced
robertbr123robertbr123

requesting-code-review

Automate code review with security scans, quality checks, and automated fixes.

Community
Advanced
nguyenphpnguyenphp
41

lint-and-validate

Run linters, type checkers, and security audits across Node.js and Python projects.

Community
Intermediate