skills.rest
nullmastermind
nullmastermindCOMMUNITY
Explore all skills by this author →
Website𝕏@nullmastermindGitHub

spx-verify

Verify implementation matches openspec artifacts and merge verifier reports.

9|9|Updated Mar 24, 2026
Search Tags:#architecture#verification#openspec#code-review#test-verification#pre-archive
One-click install
npx skills add https://github.com/nullmastermind/viber-router --skill spx-verify
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spx-verify
Source: https://github.com/nullmastermind/viber-router/tree/main/.claude/skills/spx-verify
Command: npx skills add https://github.com/nullmastermind/viber-router --skill spx-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill verifies that an implementation matches the change artifacts (specs, tasks, design) so stakeholders can confidently archive completed work without regressions or missing requirements.

Core Features & Use Cases

  • Change selection and context loading: Lists available changes and loads all context files and artifacts using openspec so verifiers operate on the real change bundle.
  • Automated verifier orchestration: Detects relevant dimensions (artifact completeness, architecture, UI/UX, tests) and runs the appropriate verifier subagents in parallel, preserving independent assessment and avoiding bias.
  • Merged, report-only output: Produces a single unified verification report with deduplicated issues classified as CRITICAL, WARNING, or SUGGESTION and recommends next steps without making any code changes.
  • Use Case: Run before archiving a feature branch to ensure tasks, specs, and implementation are complete, coherent, and safe to close.

Quick Start

Verify the implementation for change my-feature and produce a merged verification report summarizing critical, warning, and suggestion issues.

Frequently Asked Questions about spx-verify

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

FAQPage Schema
How do I verify code implementation matches specs and design documents before archiving?▼

Pre-archive verification validates that codebase changes match openspec artifacts by loading context, running parallel verifier checks, and producing a merged report without modifying code.

How does automated test verification work for feature branch changes?▼

Automated test verification detects relevant dimensions like artifact completeness and architecture, then runs appropriate verifier subagents in parallel to preserve independent assessment and avoid bias.

Can I use openspec to load context files and run verifiers on real change bundles?▼

Yes, the skill lists available changes and loads all context files and artifacts using openspec commands so verifiers operate on the real change bundle.

What is the best way to generate a unified code review report with classified issues?▼

Run parallel verifier checks to produce a single merged verification report with deduplicated issues classified as CRITICAL, WARNING, or SUGGESTION and recommended next steps.

Does pre-archive validation modify my codebase during the architecture review process?▼

No, pre-archive validation produces a report-only output summarizing verification findings and recommended next steps without making any code changes to the implementation.

Related Skills

Explore More Software Engineering Skills→
brandon-setegnbrandon-setegn

openspec-verify-change

Verify implementation matches change artifacts using the openspec CLI.

Community
Advanced
rick2047rick2047

openspec-verify-change

Verify change implementations against delta specs, tasks, and design artifacts.

Community
Advanced
dennislee928dennislee928
54

subagent-driven-development

Execute implementation plans by dispatching subagents and reviewing spec compliance and code quality.

Community
Advanced
pabloimrik17pabloimrik17

openspec-verify-change

Validate code implementations against delta specs and task artifacts.

Community
Advanced