openspec-bulk-archive-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-bulk-archive-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-bulk-archive-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-bulk-archive-change/SKILL.md

Versions recorded

1

Latest version

v1.0, committed Feb 3, 2026

Size

7,665 bytes

Repository stars

33

License

MIT

Archive multiple completed changes at once. Use when archiving several parallel changes.

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

Archive multiple completed changes in a single operation.

This skill allows you to batch-archive changes, handling spec conflicts intelligently by checking the codebase to determine what's actually implemented.

**Input**: None required (prompts for selection)

**Steps**

1. **Get active changes**

   Run `openspec list --json` to get all active changes.

   If no active changes exist, inform user and stop.

2. **Prompt for change selection**

   Use **AskUserQuestion tool** with multi-select to let user choose changes:
   - Show each change with its schema
   - Include an option for "All changes"
   - Allow any number of selections (1+ works, 2+ is the typical use case)

   **IMPORTANT**: Do NOT auto-select. Always let the user choose.

3. **Batch validation - gather status for all selected changes**

   For each selected change, collect:

   a. **Artifact status** - Run `openspec status --change "<name>" --json`
      - Parse `schemaName` and `artifacts` list
      - Note which artifacts are `done` vs other states

   b. **Task completion** - Read `openspec/changes/<name>/tasks.md`
      - Count `- [ ]` (incomplete) vs `- [x]` (complete)
…

Read the whole file at its exact version.

How to install

mdr add yazelin/ching-tech-os/openspec-bulk-archive-change@sha256:d3f369c1e67f05b6

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

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_rjnigdjxsvivigjw
GET https://markdownregistry.com/api/v1/resolve?ref=yazelin/ching-tech-os/openspec-bulk-archive-change
GET https://markdownregistry.com/api/v1/blob/d3f369c1e67f05b6b04f7da2f87bad09759307dbdc7c23773c9ef1ccc74dfb33

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-bulk-archive-change

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