openspec-verify-change

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

Verify code changes against openspec delta specs and task artifacts.

9|16|Updated Oct 16, 2018

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

Ready to run

npx skills add https://github.com/ondata/albopopTwoDotZero --skill openspec-verify-change-ondata

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/ondata/albopopTwoDotZero/tree/main/.gemini/skills/openspec-verify-change
Command: npx skills add https://github.com/ondata/albopopTwoDotZero --skill openspec-verify-change-ondata

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verify that implementations match the defined change artifacts (specs, tasks, and design) to reduce risk before archiving.

Core Features & Use Cases

Artifact alignment: Verifies consistency between code changes, task artifacts, and delta specs.
Structured verification: Generates a comprehensive report that measures completeness, correctness, and coherence.
Audit readiness: Supports repeatable validation workflows for QA and compliance reviews.

Quick Start

Run the openspec verification flow by listing changes with openspec list --json, selecting a change, and applying it with openspec instructions apply --change "<name>" to generate a verification report.

Frequently Asked Questions about openspec-verify-change

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

FAQPage Schema

How do I validate code changes against delta specs before archiving?▼

To validate code changes against delta specs before archiving, you can run an openspec verification flow to compare code implementations with task artifacts, measure completeness, and generate a structured verification report for audit readiness.

What is spec-validation for code review and how does it work?▼

Spec-validation for code review is the process of verifying that code changes match defined change artifacts. It works by searching the codebase for implementation evidence, comparing it against delta specs and design documents, and generating a structured verification report with actionable guidance.

How do I generate a verification report for change implementations?▼

You generate a verification report by listing changes with openspec list --json, selecting a target change, and applying it with openspec instructions apply --change <name>. This produces a structured report measuring completeness, correctness, and coherence of the implementation.

Does change-verification work with existing QA review workflows?▼

Yes, change-verification supports repeatable validation workflows for QA and compliance reviews. It provides audit readiness by generating structured verification reports that identify missing or divergent elements between code implementations and change artifacts.

What should I do when implementation evidence is missing from the codebase?▼

When implementation evidence is missing from the codebase, the verification process identifies these divergent elements and provides actionable guidance on the gaps. The generated structured verification report details exactly what is missing to help resolve discrepancies before archiving.