openspec-verify-change

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

Verifies code change implementations against specs, tasks, and design documents.

5|Updated Sep 17, 2022

Search Tags:#spec-driven #verification #reporting #openspec #code-review #task-tracking #change-management

Ready to run

npx skills add https://github.com/kevinxo328/mercari-scraper --skill openspec-verify-change-kevinxo328

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates verification that a code change implementation matches its change artifacts (specs, tasks, design) to ensure readiness for archiving or release and to catch missing or diverging work early.

Core Features & Use Cases

Change selection: Guides the user to select a change via openspec and inspects available artifacts for that change.
Three-dimension verification: Checks completeness (task checklists and requirement presence), correctness (implementation vs. requirements and scenario coverage), and coherence (design adherence and code pattern consistency).
Actionable reporting: Produces prioritized CRITICAL/WARNING/SUGGESTION issues with file references and concrete remediation recommendations to drive fixes and approvals.

Quick Start

Run openspec-verify-change and choose the change you want to validate, then review the generated verification report for critical issues and recommendations.

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 against specs and design documents before deployment?▼

To verify code changes against specs, an automated verification process checks implementation completeness, correctness, and coherence against change artifacts. It inspects tasks.md, delta specs, and design.md to ensure readiness for archiving or release and catch diverging work early.

What is spec-driven verification for change management?▼

Spec-driven verification is the process of validating that a code change implementation matches its change artifacts like specs, tasks, and design documents. It assesses completeness, correctness, and coherence to confirm readiness before archiving or deployment.

Do I need the openspec CLI to track and validate change status?▼

Yes, validating change status with this approach requires the openspec CLI. The CLI is used to list changes, retrieve status, and gather context files needed to inspect tasks.md, delta specs, and design.md for completeness assessment.

How do I generate a code review report for task tracking and change readiness?▼

You can generate an actionable code review report by running a verification check on your selected change. The process produces prioritized CRITICAL, WARNING, and SUGGESTION issues with file references and concrete remediation recommendations to drive fixes and approvals.

What does implementation coherence checks cover in spec-driven code review?▼

Implementation coherence checks cover design adherence and code pattern consistency during spec-driven code review. This dimension ensures the implementation aligns with the documented design and follows established patterns across the codebase.

Can I use automated verification to catch missing tasks before archiving a change?▼

Yes, automated verification catches missing tasks before archiving by checking task checklists and requirement presence. It reviews available artifacts for the selected change to identify incomplete or diverging work early in the process.