openspec-update-change SKILL.md skillA

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

openspec-update-change from partcad/partcad is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

mdr add partcad/partcad/openspec-update-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

partcad/partcad

Path

.cursor/skills/openspec-update-change/SKILL.md

Versions recorded

1

Latest version

v1.0, committed Jul 21, 2026

Size

5,791 bytes

Repository stars

514

License

Apache-2.0

Update an OpenSpec change by revising its existing planning artifacts and keeping them coherent with one another. Use when the user wants to revise a change's plan, fold new decisions into it, or reconcile its artifacts after an edit. Never edits code.

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

Revise a change's existing planning artifacts and keep them coherent. Never edit code.

**Store selection:** If the user names a store (a store is a standalone OpenSpec repo registered on this machine) or the work lives in one, run `openspec store list --json` to discover registered store ids, then pass `--store <id>` on the commands that read or write specs and changes (`new change`, `status`, `instructions`, `list`, `show`, `validate`, `archive`, `doctor`, `context`). Other commands do not take the flag. Hints printed by commands already carry the flag; keep it on follow-ups. Without a store, commands act on the nearest local `openspec/` root.

**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 sorted by most recently modified. Then use the **AskUserQuestion tool** to let the user select which change to update.

   Present the top 3-4 most recently modified changes as options, showing:
   - Change name
…

Read the whole file at its exact version.

How to install

mdr add partcad/partcad/openspec-update-change@sha256:82a51ed50b10ac3b

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

Versions

The registry has recorded 1 version of this file, committed on Jul 21, 2026.

Audit of the latest version

Source

API

GET https://markdownregistry.com/api/v1/artifacts/art_qsivy4g33sjdmhb6
GET https://markdownregistry.com/api/v1/resolve?ref=partcad/partcad/openspec-update-change
GET https://markdownregistry.com/api/v1/blob/82a51ed50b10ac3be479d7abc4a99fe3685ee7794078d7d8ea7bfc90ae42c2d9

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 partcad/partcad

Every file in partcad/partcad

Other files named openspec-update-change

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