openspec-verify-change SKILL.md skillA

This file is byte-identical to the first copy the registry indexed, one of 4 indexed copies. Same content hash, so the same checks give both the same grade.

openspec-verify-change from yazelin/ching-tech-os is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

mdr add yazelin/ching-tech-os/openspec-verify-change@v1.0

Pins v1.0 in mdr.lock. Pin the fingerprint instead.

Audit grade

A, 17 of 17 checks passed

Kind

SKILL.md skill

Repository

yazelin/ching-tech-os

Path

.claude/skills/openspec-verify-change/SKILL.md

Versions recorded

1

Latest version

v1.0, committed Feb 3, 2026

Size

6,541 bytes

Repository stars

33

License

MIT

Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

Verify that an implementation matches the change artifacts (specs, tasks, design).

**Input**: Optionally specify a change name. If omitted, check if it can be inferred from conversation context. If vague or ambiguous you MUST prompt for available changes.

**Steps**

1. **If no change name provided, prompt for selection**

   Run `openspec list --json` to get available changes. Use the **AskUserQuestion tool** to let the user select.

   Show changes that have implementation tasks (tasks artifact exists).
   Include the schema used for each change if available.
   Mark changes with incomplete tasks as "(In Progress)".

   **IMPORTANT**: Do NOT guess or auto-select a change. Always let the user choose.

2. **Check status to understand the schema**
   ```bash
   openspec status --change "<name>" --json
   ```
   Parse the JSON to understand:
   - `schemaName`: The workflow being used (e.g., "spec-driven")
   - Which artifacts exist for this change

3. **Get the change directory and load artifacts**

   ```bash
   openspec instructions apply --change "<name>" --json
   ```

   This returns the change directory and context files. Read all available artifacts from `contextFiles`.
…

Read the whole file at its exact version.

How to install

mdr add yazelin/ching-tech-os/openspec-verify-change@sha256:94c988710e2a0232

[![mdr](https://markdownregistry.com/badge/art_2orqlx76ojlpk6tp.svg)](https://markdownregistry.com/a/art_2orqlx76ojlpk6tp)

Versions

The registry has recorded 1 version of this file, committed on Feb 3, 2026.

Audit of the latest version

Source

API

GET https://markdownregistry.com/api/v1/artifacts/art_2orqlx76ojlpk6tp
GET https://markdownregistry.com/api/v1/resolve?ref=yazelin/ching-tech-os/openspec-verify-change
GET https://markdownregistry.com/api/v1/blob/94c988710e2a023267693792d262cec67c402ede77fcc898b632c2b3f5959356

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from yazelin/ching-tech-os

Every file in yazelin/ching-tech-os

Other files named openspec-verify-change

Browse by kind, by grade A, or by owner.