openspec-verify-change

Verify code implementations against change artifacts using the acfm CLI.

Updated Feb 19, 2026

Search Tags:#quality assurance #code review #verification #change management #spec compliance #acfm

Ready to run

npx skills add https://github.com/B4san/Calix-Pass --skill openspec-verify-change-b4san

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-verify-change
Source: https://github.com/B4san/Calix-Pass/tree/main/.gemini/skills/openspec-verify-change
Command: npx skills add https://github.com/B4san/Calix-Pass --skill openspec-verify-change-b4san

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill ensures that code implementations accurately reflect the defined change artifacts, preventing discrepancies and ensuring quality before archiving.

Core Features & Use Cases

Completeness Check: Verifies that all defined tasks and requirements are addressed in the implementation.
Correctness Validation: Assesses if the code correctly implements specified requirements and covers defined scenarios.
Coherence Assessment: Checks for adherence to design decisions and consistency with project coding patterns.
Use Case: After a developer implements a new feature based on a specification, this Skill can be used to automatically verify that all aspects of the specification have been met and that the implementation aligns with the project's design principles.

Quick Start

Use the openspec-verify-change skill to verify the implementation for the change named 'user-authentication-flow'.

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 implementation against change artifacts and specifications?▼

Verifying code implementation against change artifacts involves checking completeness, correctness, and coherence by analyzing code against tasks, requirements, and design documents using the acfm CLI to ensure quality before archiving changes.

What does spec compliance checking include in a software development workflow?▼

Spec compliance checking includes validating that all defined tasks and requirements are addressed, assessing if code correctly implements specified scenarios, and verifying adherence to design decisions and project coding patterns.

How do I check if my feature implementation meets all defined change requirements?▼

Checking if a feature implementation meets defined change requirements requires analyzing the code against change artifacts to assess completeness, correctness, and coherence using the acfm CLI before archiving.

Do I need the acfm CLI to run change verification and spec compliance checks?▼

Yes, the acfm CLI is required as a dependency to analyze code against change artifacts, assess implementation completeness, and validate coherence with project coding patterns.

When should I run change verification in the code review process?▼

Change verification should be run after a developer implements a new feature based on a specification, ensuring all aspects of the specification are met and the implementation aligns with design principles before archiving changes.

What is the best way to automate quality assurance for change management before archiving?▼

Automating quality assurance for change management is best achieved by verifying implementation against change artifacts to prevent discrepancies, assessing completeness, correctness, and coherence using the acfm CLI before archiving.