openspec-verify-change

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

Verify changes against delta specifications and artifacts using the openspec CLI.

Updated Mar 4, 2026

Search Tags:#quality-assurance #verify #openspec #code-review #change-artifacts #delta-specs

Ready to run

npx skills add https://github.com/kunish/muon --skill openspec-verify-change-kunish

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verifies that implemented changes align with delta specifications and associated artifacts before archiving, ensuring traceability and quality control.

Core Features & Use Cases

Validate that changes correspond to the specified tasks and design artifacts.
Generate a structured verification report covering Completeness, Correctness, and Coherence.
Integrate with the openspec CLI to fetch available changes and artifact context, enabling confident archiving decisions.

Quick Start

Run the verification workflow against a target change to confirm implementation alignment and readiness for archiving.

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 changes against delta specifications before archiving?▼

To verify changes against delta specifications before archiving, you can run a verification workflow that uses the openspec CLI to list changes, inspect statuses, and load artifacts to compute findings across Completeness, Correctness, and Coherence.

What is a change artifact verification report and what does it include?▼

A change artifact verification report validates that implemented changes align with delta specifications, generating structured findings across Completeness, Correctness, and Coherence to ensure traceability and quality control before archiving.

Do I need the openspec CLI to validate change readiness for archiving?▼

Yes, you need the openspec CLI and access to change artifacts to validate change readiness for archiving, as the CLI is used to list available changes, inspect statuses, and load the artifact context required to compute verification findings.

How do I check if implemented code matches design artifacts and tasks?▼

You can check if implemented code matches design artifacts by running a verification workflow that fetches artifact context via the openspec CLI and generates a structured report confirming implementation alignment with specified tasks and design artifacts.

What is the best way to ensure traceability and quality control before archiving code changes?▼

The best way to ensure traceability and quality control before archiving is to validate implemented changes against delta specifications using a structured verification report, which confirms alignment with tasks and design artifacts for confident archiving decisions.