openspec-verify-change

Validate code changes against openspec delta specs and generate verification reports.

Updated Feb 1, 2026
One-click install
npx skills add https://github.com/brainsnorkel/channel-secrets --skill openspec-verify-change-brainsnorkel
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/brainsnorkel/channel-secrets/tree/main/.claude/skills/openspec-verify-change
Command: npx skills add https://github.com/brainsnorkel/channel-secrets --skill openspec-verify-change-brainsnorkel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validate that a code change implements the corresponding specifications and deltas before archiving.

Core Features & Use Cases

  • Automated delta-spec alignment: verify that code changes satisfy the requirements documented in openspec delta specs.
  • Artifact-driven verification: cross-checks tasks, design artifacts, and schemas, generating a structured report.
  • Archival readiness: produce a concise, actionable report highlighting gaps and remediation steps.

Quick Start

Run the openspec verify-change command for the target change to confirm the implementation matches the change artifacts.

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 match specifications before archiving?

To verify code changes match specifications before archiving, run the openspec verify-change command. It analyzes delta specs, tasks, and design artifacts, then produces a structured report confirming implementation completeness and correctness.

What is automated delta-spec alignment for code quality?

Automated delta-spec alignment is the process of cross-checking code changes against documented openspec delta specs. It validates that implementation satisfies the requirements documented in delta specs, tasks, and design artifacts, generating a structured verification report.

How do I check archival readiness for a specification change?

Check archival readiness by applying delta specs and design artifacts to the codebase to produce a structured verification report. This report highlights completeness gaps and provides actionable remediation steps to confirm the change is ready to be archived.

Can I use artifact-driven verification to cross-check design artifacts and tasks?

Yes, artifact-driven verification cross-checks tasks, design artifacts, and schemas against the codebase. It applies these artifacts to validate coherence across the change and generates an actionable report detailing any implementation gaps.

What is the best way to validate implementation completeness for a code change?

The best way to validate implementation completeness is to use artifact-driven retrieval and context loading to analyze delta specs. This approach produces a structured report covering correctness and coherence, confirming the code change satisfies the specifications.

Why does spec validation report gaps and remediation steps before archiving?

Spec validation reports gaps and remediation steps to ensure the code change fully implements the corresponding specifications and deltas before archiving. This actionable reporting highlights missing requirements, preventing incomplete changes from being archived.