openspec-verify-change

Verify code changes against openspec delta specs and generate structured reports.

Updated Dec 28, 2025
One-click install
npx skills add https://github.com/oalansilva/crypto --skill openspec-verify-change-oalansilva
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/oalansilva/crypto/tree/main/.codex/skills/openspec-verify-change
Command: npx skills add https://github.com/oalansilva/crypto --skill openspec-verify-change-oalansilva

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This verification skill helps development teams ensure that a given change implementation fully aligns with its change artifacts (specs, tasks, and design) before archiving, reducing risk of incomplete or divergent work.

Core Features & Use Cases

  • Delta-spec alignment: cross-checks implemented code against delta specs to confirm requirements are addressed.
  • Artifact-aware validation: loads available artifacts (tasks, specs, design) and assesses completeness, correctness, and coherence.
  • Actionable reporting: produces a structured verification report that highlights critical gaps and recommended fixes for auditors or CI processes.

Quick Start

Run the verification workflow for a target change using openspec.

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 align with software specs before archiving?

You can verify code changes against specs by parsing contextFiles, mapping requirements to the implementation, and generating a structured report to highlight gaps. This ensures implementation matches delta specs, tasks, and design artifacts before archiving.

What is delta spec alignment and how does artifact validation work?

Delta spec alignment cross-checks implemented code against change artifacts to confirm requirements are addressed. Artifact validation loads available tasks, specs, and design documents to assess the completeness, correctness, and coherence of the code change.

Can I use openspec artifacts for automated code review in a CI process?

Yes, you can use openspec artifacts for automated code review in CI processes. The validation generates a structured verification report with actionable recommendations, highlighting critical gaps and recommended fixes suitable for CI integration.

How do I map requirements to code when checking change implementation completeness?

To map requirements to code, the verification process parses contextFiles from your openspec change artifacts. It then cross-checks these delta specs against the implementation to assess completeness and generate a report of actionable fixes.

What is the best way to produce a structured report for incomplete code changes?

The best way to produce a structured report is by running an artifact-aware validation. It loads available tasks, specs, and design documents, assesses coherence, and outputs a report highlighting critical gaps and recommended fixes for auditors.