665,000+ skills indexed

zthxxxCOMMUNITY

Explore all skills by this author →

Verified:𝕏@zthxxxxx GitHub

openspec-verify-change

Validate software implementations against change specifications and scenarios.

Updated Apr 4, 2026

Search Tags:#automation #code review #specification #implementation #verification #change management

One-click install

npx skills add https://github.com/zthxxx/hams --skill openspec-verify-change-zthxxx

Or copy as Structured Prompt for Agent▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires openspec, and includes scripts (resource) components.

What problem does it solve?

This Skill enables teams to verify that their implementation aligns with specified change artifacts, ensuring completeness, correctness, and coherence before archiving or deployment.

Core Features & Use Cases

Implementation Verification: Checks if code fulfills requirements and scenarios derived from change specifications.
Artifact Analysis: Uses openspec CLI to extract relevant change details, schemas, and context files.
Use Case: Developers can run this Skill to verify whether their recent code changes fully implement specified requirements and scenarios, reducing integration errors.

Quick Start

Use the openspec-verify-change Skill to confirm if your recent implementation matches the change specifications before archiving.

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 match change specifications before deployment?▼

To verify code changes match change specifications, you can validate implementation consistency by analyzing specifications, tasks, and scenarios to ensure code modifications align with change artifacts before archiving or deployment.

What is change artifact verification in software development workflows?▼

Change artifact verification is the process of checking if code fulfills requirements and scenarios derived from change specifications, ensuring completeness, correctness, and coherence during development and review workflows.

How do I check if my implementation fulfills requirements from a change specification?▼

You check implementation fulfillment by extracting relevant change details, schemas, and context files using the openspec CLI, then analyzing them against your code to confirm requirements and scenarios are fully implemented.

Does openspec-verify-change require the openspec CLI to extract change details?▼

Yes, openspec-verify-change requires the openspec dependency, using its CLI to extract relevant change details, schemas, and context files needed to validate implementation consistency against the artifacts.

Can I use this verification skill to reduce integration errors during code review?▼

Yes, you can use this skill during code review to verify whether recent code changes fully implement specified requirements and scenarios, effectively reducing integration errors before archiving modifications.

When should I run implementation verification against change artifacts?▼

You should run implementation verification against change artifacts before archiving or deployment, ensuring that recent code changes fully align with specified requirements and scenarios to maintain quality and completeness.

Related Skills

Explore More Software Engineering Skills→

openspec-continue-change

Generate the next required OpenSpec artifact from current workflow status.

openspec-archive-change

Archive a completed OpenSpec change with validated artifacts and metadata.

openspec-verify-change

Validate change implementation against delta specs and code evidence.

SufficientDaikon

reviewer

Automates compliance review of implementation code against specification files and generates HTML reports.