openspec-verify-change

Verify code implementations against openspec change artifacts using the openspec CLI.

133|23|Updated Mar 23, 2020

Search Tags:#testing #code review #implementation #verification #change management #openspec

Ready to run

npx skills add https://github.com/aehrc/pathling --skill openspec-verify-change-aehrc

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill ensures that code implementations accurately reflect the intended design, specifications, and tasks defined for a change, preventing inconsistencies and ensuring quality before archiving.

Core Features & Use Cases

Automated Verification: Checks for completeness, correctness, and coherence between code and change artifacts.
Artifact Analysis: Parses tasks.md, spec requirements, and design documents.
Use Case: Before merging a new feature, use this Skill to confirm that all defined requirements are implemented, scenarios are covered, and the code adheres to 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 requirements?▼

You can verify code implementation against change artifacts by using automated verification to check completeness, correctness, and coherence between your codebase and specifications. It analyzes tasks, requirements, and design documents to ensure alignment before archiving changes.

What is the best way to automate code review for design document adherence?▼

Automating code review for design document adherence involves parsing change artifacts like `tasks.md` and spec requirements to confirm all defined requirements are implemented and scenarios are covered. This ensures code adheres to project design principles before merging.

Do I need the openspec CLI to check if implementation aligns with specifications?▼

Yes, you need the openspec CLI installed to interact with change management data and analyze codebase adherence to specifications. The verification process relies on this dependency to access and parse the required change artifacts.

Can I check development workflow coherence and completeness before merging a feature?▼

Yes, you can check development workflow coherence and completeness before merging a feature by running an automated verification assessment. It confirms that all defined tasks, requirements, and design specifications are accurately reflected in the code implementation.

How does artifact analysis parse tasks.md and spec requirements for code review?▼

Artifact analysis parses `tasks.md`, spec requirements, and design documents to compare them directly against code implementations. It assesses whether the code correctly implements the specified scenarios and fulfills the intended design without inconsistencies.