skills.rest
tonysyu
tonysyuCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

openspec-verify-change

Validate code changes against openspec delta specs and task lists.

2|Updated Sep 23, 2025
Search Tags:#testing#code-quality#verify#openspec#spec-validation#change-artifacts#delta-specs
One-click install
npx skills add https://github.com/tonysyu/gqlxp --skill openspec-verify-change-tonysyu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/tonysyu/gqlxp/tree/main/.claude/skills/openspec-verify-change
Command: npx skills add https://github.com/tonysyu/gqlxp --skill openspec-verify-change-tonysyu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verify that changes implemented in code align with their change artifacts (specs, tasks, and design) to ensure coherence before archiving.

Core Features & Use Cases

  • Delta-spec parsing and validation against code changes
  • Status checks against openspec artifacts and task lists
  • Coherence analysis across design decisions and implemented behavior
  • Automated generation of a structured verification report with actionable recommendations

Quick Start

Provide a change name and ask the tool to run a verification pass against the associated artifacts.

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 my code changes match the design specs before archiving?▼

To verify code matches design specs before archiving, you validate delta specs and task lists against the implementation. This process checks task completion, spec coverage, and design coherence to output a structured report with actionable issues.

What does spec validation against code changes actually check?▼

Spec validation checks that implemented behavior aligns with delta specs, task lists, and design artifacts. It parses openspec context files, inspects code for requirements, and reports CRITICAL, WARNING, and SUGGESTION issues for any mismatches.

How do I check task list completion status against openspec artifacts?▼

You can check task list completion by running a verification pass against the openspec change artifacts. The tool reads context files from the openspec/changes directory and identifies incomplete tasks or missing spec coverage in the generated report.

Does openspec-verify-change work without delta specs stored in the changes directory?▼

No, openspec-verify-change requires changes to have delta specs and artifacts stored under openspec/changes/<change>/. It reads these context files directly to parse delta specs and perform coherence analysis before generating its verification report.

What is the best way to identify coverage gaps in my software change artifacts?▼

The best way to identify coverage gaps is to run an automated validation pass on your change artifacts. This checks scenario coverage and spec coherence against the actual code, highlighting missing requirements in a structured verification report.

Why does my implementation fail spec validation even when tasks are marked complete?▼

Spec validation may fail because the implementation behavior lacks design coherence with the delta specs, or scenario coverage is incomplete. The tool inspects code for requirements and flags these discrepancies as CRITICAL or WARNING issues in the report.

Related Skills

Explore More Software Engineering Skills→
SiddharthChillaleSiddharthChillale

openspec-verify-change

Verify implementation alignment with OpenSpec change artifacts and generate a report.

Community
Advanced
Gentleman-ProgrammingGentleman-Programming
1.3k

sdd-archive

Merge delta specs into main specs and archive completed changes.

Official
Advanced
belingudbelingud
30

openspec-verify-change

no

Community
Advanced
yonyon
3

lint

Run linters and static analysis tools with severity-based output and auto-fix mode.

Community
Basic