skills.rest
TE-QuanBZhang
TE-QuanBZhangCOMMUNITY
Explore all skills by this author →
GitHub

opsx-verify

Verifies OpenSpec changes by running tests, linting, and code quality checks.

1|Updated Jun 27, 2026
Search Tags:#code quality#testing#linting#slash command#verify#openspec#codegraph
One-click install
npx skills add https://github.com/TE-QuanBZhang/skills-pool --skill opsx-verify-te-quanbzhang
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: opsx-verify
Source: https://github.com/TE-QuanBZhang/skills-pool/tree/main/ai-coding/skills/opsx-verify
Command: npx skills add https://github.com/TE-QuanBZhang/skills-pool --skill opsx-verify-te-quanbzhang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After applying a change in an OpenSpec workflow, developers need a structured way to confirm the code compiles, passes tests, and meets quality standards before archiving. This Skill automates that verification step via the /opsx:verify slash command. ## Core Features & Use Cases - Structured verification pipeline: Runs formatting checks, clippy linting, tests, and argument-comment lint in sequence, reporting pass/fail for each. - OpenSpec integration: Selects the target change, checks its status with openspec status --change, and validates the implementation against the change proposal. - CodeGraph context: Uses codegraph explore and codegraph sync to keep the code index current before running checks. - Use Case: After running /opsx:apply to implement a change like add-auth, invoke /opsx:verify add-auth to confirm the new code compiles, passes the test suite, and satisfies lint rules before archiving. ## Quick Start Ask the AI to run /opsx:verify on your current OpenSpec change to validate that it compiles, passes tests, and meets quality standards.

Frequently Asked Questions about opsx-verify

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

FAQPage Schema
How do I verify an OpenSpec change after applying it?▼

Run the /opsx:verify slash command, optionally followed by the change name such as /opsx:verify add-auth. It checks the change status, syncs the CodeGraph index, then runs formatting, clippy, tests, and lint checks with a structured pass/fail report.

What checks does the opsx verify command run?▼

It runs four categories of checks in sequence: code formatting, clippy linting, the test suite, and an argument-comment lint. Results are reported as a structured pass/fail summary for each check.

Does opsx-verify require the openspec CLI?▼

Yes, the openspec CLI is required to query change status via openspec status --change. The skill also uses the codegraph CLI to explore and sync the code index before running verification checks.

When should I run /opsx:verify in the OpenSpec workflow?▼

Run it after /opsx:apply has implemented a change and before archiving it. Verification confirms the implementation compiles, passes tests, and meets quality standards so incomplete changes are not archived.

What happens if I don't specify a change name to /opsx:verify?▼

The change name is optional. If omitted or ambiguous, the workflow prompts you to select the correct change before proceeding with status checks and verification.

Related Skills

Explore More Software Engineering Skills→
Chorus-AIDLCChorus-AIDLC
1.2k

openspec-propose

Generates a complete OpenSpec change proposal with design, specs, and task artifacts.

Official
Intermediate
juanjo-zurichjuanjo-zurich

sdd-archive

Merges delta specs into main specs and archives completed SDD changes.

Community
Advanced
stark-ai-destark-ai-de
4

codegraph-ast-grep

Integrate CodeGraph and ast-grep for semantic repository maps and structural search.

Official
Advanced
nodesourcenodesource
6

detect-stack-and-update-config

Detects project tech stack and tooling, then updates openspec/config.yaml with findings.

Official
Intermediate