openspec-verify-change

Name: openspec-verify-change
Availability: InStock
Author: wzyxdwll

Verify delta specs against code and tests with a structured report.

14|1|Updated May 6, 2026

Search Tags:#automation #openspec #code-review #artifact-validation #change-verification #spec-review

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams ensure that code changes align with the defined specifications and tasks before archiving, reducing misalignment and rework.

Core Features & Use Cases

Automated delta-spec verification against code and tasks
Cross-reference of specs, tasks, and design notes to surface gaps
Generate a structured verification report with prioritized issues and recommendations

Quick Start

Select a change name from the openspec list and run the verification workflow.

Frequently Asked Questions about openspec-verify-change

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

FAQPage Schema

How do I verify code changes against delta specs in openspec?▼

To verify code changes against delta specs, this Skill analyzes openspec/changes/<name>/specs/ to extract requirements and map them to your repository code and tests, generating a structured verification report.

What is artifact validation for software change implementation?▼

Artifact validation for change implementation is the process of cross-referencing delta specs, tasks, and design notes to surface gaps, ensuring code changes align with defined specifications before archiving.

How do I generate a structured code review report for spec misalignment?▼

You generate a structured code review report by running the verification workflow, which highlights CRITICAL, WARNING, and SUGGESTION issues with actionable recommendations for spec misalignment.

Do I need to manually select a change name to start the openspec verification workflow?▼

You do not need to manually select a change name if omitted; the workflow will automatically identify the target change by name using openspec or prompt you for input to proceed.

Can I use this to surface gaps between design notes and repository tests?▼

You can use this to surface gaps between design notes and repository tests by cross-referencing the extracted requirements and scenarios from your delta specs against the actual codebase implementation.

What are the limitations of automated change verification before archiving?▼

Limitations of automated change verification include relying entirely on the accuracy of your delta specs under openspec/changes/ to map requirements and identify code misalignment, meaning poorly written specs will yield incomplete reports.