openspec-verify-change

Validate code implementations against delta specs and task artifacts.

Updated Apr 11, 2025
One-click install
npx skills add https://github.com/pabloimrik17/monolab --skill openspec-verify-change-pabloimrik17
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/pabloimrik17/monolab/tree/main/.junie/skills/openspec-verify-change
Command: npx skills add https://github.com/pabloimrik17/monolab --skill openspec-verify-change-pabloimrik17

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verify that an implementation matches the change artifacts (specs, tasks, and design context).

Core Features & Use Cases

  • Provides a structured approach to validate that code changes implement the delta specs and tasks.
  • Generates a verification report describing completeness, correctness, and coherence.
  • Supports graceful degradation when one or more artifacts are missing, with clear guidance.

Quick Start

Provide the change name to verify and run the verification process.

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 tasks?

Verify code changes by parsing change artifacts, locating relevant code, and assessing coverage against requirements to produce a structured report on completeness and correctness.

What is change implementation verification?

Change implementation verification validates that delta specs, task artifacts, and code align correctly, assessing coherence and completeness to determine if an implementation matches the defined design context.

How do I check if my code implementation matches design specs?

Check implementation alignment by applying verification processes that compare code against delta specs and tasks, generating a structured report describing completeness, correctness, and coherence.

Can I verify a change if some task artifacts are missing?

Yes, verification supports graceful degradation when artifacts are missing, providing clear guidance in the structured report to handle incomplete specs, tasks, or design context.

What does a code verification report include?

A verification report describes completeness, correctness, and coherence across delta specs, task artifacts, and code, detailing how well the implementation matches the defined change artifacts.

When do I need to verify change artifacts?

Verify change artifacts during change verification to determine if an implementation matches defined specs, tasks, and design context, ensuring code changes align with requirements.