openspec-verify-change

Verify change implementations against openspec delta specs and design artifacts.

2|2|Updated Sep 20, 2023

Search Tags:#verify #openspec #code-review #specs #change #artifact-analysis

Ready to run

npx skills add https://github.com/zabiny/klabis --skill openspec-verify-change-zabiny

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verifies that a change's implementation aligns with its associated specs, tasks, and design artifacts to ensure coherence before archiving or release.

Core Features & Use Cases

Load and analyze change artifacts via openspec, comparing delta specs, tasks, and design decisions.
Generate a structured verification report with CRITICAL, WARNING, and SUGGESTION issues plus actionable recommendations.
Identify gaps such as incomplete tasks, missing requirement implementations, or design deviations, and provide file/line references for remediation.

Quick Start

Trigger a verification workflow by selecting a change with openspec and applying the verification to generate a report.

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 design specs and task artifacts?▼

To verify code changes against design specs, you need a tool that compares delta specs, tasks, and codebase artifacts to determine completeness and coherence. This process generates a structured verification report with prioritized, actionable recommendations and file paths for any gaps or divergences.

What is a structured verification report for software change implementations?▼

A structured verification report for change implementations identifies gaps, incomplete tasks, and design deviations by comparing code against specs. It categorizes issues into CRITICAL, WARNING, and SUGGESTION levels, providing file and line references for targeted remediation.

How do I identify missing requirement implementations in a codebase?▼

You can identify missing requirement implementations by analyzing context artifacts and delta specs across the codebase. This comparison validates completeness and correctness, returning a prioritized set of actionable recommendations with exact file paths and line references for any found gaps.

When do I need to validate change implementations against specs?▼

You need to validate change implementations against specs before archiving or releasing a change. This ensures the implementation aligns with associated tasks, design artifacts, and delta specs, verifying overall coherence and preventing incomplete requirements from progressing.

Can I get file and line references for design deviations found during code review?▼

Yes, validating change implementations against specs can produce file and line references for design deviations. By operating across delta specs and the codebase, it generates a structured report with prioritized, actionable recommendations for precise remediation.