openspec-verify-change

To verify code changes against delta specs, this Skill analyzes openspec/changes/<name>/specs/ to extract requirements and map them to your repository code and tests, generating a structured verification report.

Artifact validation for change implementation is the process of cross-referencing delta specs, tasks, and design notes to surface gaps, ensuring code changes align with defined specifications before archiving.

You generate a structured code review report by running the verification workflow, which highlights CRITICAL, WARNING, and SUGGESTION issues with actionable recommendations for spec misalignment.

You do not need to manually select a change name if omitted; the workflow will automatically identify the target change by name using openspec or prompt you for input to proceed.

You can use this to surface gaps between design notes and repository tests by cross-referencing the extracted requirements and scenarios from your delta specs against the actual codebase implementation.

Limitations of automated change verification include relying entirely on the accuracy of your delta specs under openspec/changes/ to map requirements and identify code misalignment, meaning poorly written specs will yield incomplete reports.