opsx-verify

Cross-reference change artifacts against specifications and tests to produce a verification report.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/ConductionNL/decidesk --skill opsx-verify-conductionnl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: opsx-verify
Source: https://github.com/ConductionNL/decidesk/tree/main/.claude/skills/opsx-verify
Command: npx skills add https://github.com/ConductionNL/decidesk --skill opsx-verify-conductionnl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates a rigorous verification workflow to ensure that implemented changes align with change artifacts, specifications, and tests before archiving, reducing risk of regressions and misalignment.

Core Features & Use Cases

  • Coordinates completeness, correctness, and coherence checks across tasks, delta specs, design docs, and tests.
  • Generates a consolidated verification report with actionable recommendations and an archive decision.
  • Optionally runs API and browser tests to validate end-to-end behavior against specifications.

Quick Start

Run /opsx-verify on a change to begin the automated verification workflow.

Frequently Asked Questions about opsx-verify

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify code changes against specifications before archiving?

To verify code changes against specifications, you can run an automated workflow that cross-references tasks, delta specs, design docs, and tests to produce a structured verification report with an archive decision.

What is automated change verification in GitHub?

Automated change verification in GitHub systematically assesses the completeness, correctness, and coherence of implemented changes by loading repository artifacts and validating them against specifications.

Can I run API and browser tests during the code review process?

Yes, you can optionally run API and browser tests during code review to validate end-to-end behavior against the specifications and ensure the changes function correctly.

What is the best way to coordinate completeness and correctness checks for repository changes?

The best way to coordinate completeness and correctness checks is using an automated verification workflow that cross-references delta specs, design docs, and tests to generate a consolidated report with actionable recommendations.

How do I generate a verification report detailing issues and recommendations for code changes?

You generate a verification report by identifying a change, loading its repository artifacts, and cross-referencing them against specifications to detail issues, recommendations, and a ready-to-archive decision.

When do I need to run a coherence check on delta specs and design docs?

You need to run a coherence check on delta specs and design docs when you want to ensure implemented changes align with change artifacts and tests before archiving, reducing the risk of regressions.