openspec-verify-change

Verify code changes against openspec artifacts and generate a prioritized report.

Updated Mar 16, 2026
One-click install
npx skills add https://github.com/chuangkevin/project-bridge --skill openspec-verify-change-chuangkevin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/chuangkevin/project-bridge/tree/main/.gemini/skills/openspec-verify-change
Command: npx skills add https://github.com/chuangkevin/project-bridge --skill openspec-verify-change-chuangkevin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensure that a code change is complete, correct, and coherent with its change artifacts before archiving, preventing incomplete releases and unnoticed spec or design divergences.

Core Features & Use Cases

  • Interactive change selection: Prompts the reviewer to choose a change that has implementation tasks, avoiding accidental guesses.
  • Artifact-driven verification: Uses openspec CLI outputs (list, status, instructions) to load tasks.md, delta specs, and design artifacts and checks for missing tasks, unimplemented requirements, and uncovered scenarios.
  • Three-dimension report: Produces a structured report covering Completeness (task and spec coverage), Correctness (requirement-to-implementation mapping and scenario coverage), and Coherence (design adherence and code pattern consistency) with CRITICAL/WARNING/SUGGESTION priorities and actionable recommendations.

Quick Start

Run the openspec verification flow for the named change, select the change when prompted, and generate the verification report to see completeness, correctness, and coherence issues.

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 implementation matches change artifacts before archiving?

To verify implementation matches change artifacts, the Skill loads spec deltas, tasks.md, and design artifacts via openspec CLI to identify missing tasks, unimplemented requirements, and design divergences before archiving.

What is change artifact verification in software engineering?

Change artifact verification assesses code completeness, correctness, and coherence by mapping requirement-to-implementation relationships and checking task coverage against spec deltas to prevent incomplete releases.

Do I need the openspec CLI to check for unimplemented requirements in a change?

Yes, openspec CLI access is required to run list, status, and instructions commands and read contextFiles, which extracts the task and spec data needed to produce the verification report.

How do I check code change completeness and coherence using spec validation?

Spec validation checks completeness by verifying task and spec coverage, correctness by mapping requirements to implementation, and coherence by assessing design adherence, outputting prioritized CRITICAL, WARNING, and SUGGESTION recommendations.

What's the best way to identify missing tasks and design divergences in code review?

Use artifact-driven verification to compare implementation against tasks.md and design artifacts, generating a structured report that highlights uncovered scenarios and design divergences with actionable recommendations.