openspec-verify-change

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

Verify code changes against openspec tasks, specs, and design artifacts.

4|3|Updated Jan 16, 2023

Search Tags:#qa #archiving #verify #openspec #code-review #specs #change

Ready to run

npx skills add https://github.com/sgiath/secp256k1 --skill openspec-verify-change-sgiath

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This verification workflow helps teams ensure that a code change aligns with its change artifacts (specs, tasks, and design) before it is archived.

Core Features & Use Cases

Spec-coverage verification: compares delta specs against code and artifacts to identify missing implementations.
Task-completion validation: checks if tasks are marked complete and tracks remaining work.
Coherence assessment: evaluates design decisions and coding patterns for consistency.
Use Case: When preparing a change for release, run this skill to confirm all requirements are met and the change is ready for archiving.

Quick Start

Run the openspec verification on your change to check tasks, specs, and design 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 a code change matches its specs and tasks before archiving?▼

You can verify change implementations by parsing specs, tasks, and design artifacts to check for gaps. This automated workflow enforces task completion and spec coverage to ensure your code change is coherent and ready for archival.

What is spec-coverage verification in a change archival workflow?▼

Spec-coverage verification compares delta specs against your code and artifacts to identify missing implementations. It ensures that every requirement defined in the change artifacts has been addressed before the change is archived.

How do I validate task completion for a code change using openspec?▼

Task-completion validation checks if your change tasks are marked complete and tracks any remaining work. It parses your openspec task artifacts to report gaps and ensure all required work is finished before release.

Can I assess design coherence and coding patterns automatically before archiving a change?▼

Yes, coherence assessment evaluates your design decisions and coding patterns for consistency. It checks that the implemented change aligns with the design artifacts, ensuring overall coherence and readiness for the archival process.

Does openspec change verification work without additional dependencies?▼

Yes, this verification workflow runs without external dependencies. It directly parses your openspec tasks, specs, and delta artifacts to report gaps and confirm readiness for archiving your code changes.

What are the limitations of automating change verification before archival?▼

The verification process is limited to parsing existing openspec artifacts to enforce task completion and spec coverage. It cannot evaluate gaps if your change artifacts lack defined specs, tasks, or design decisions.