openspec-update-change SKILL.md skillA
openspec-update-change from asymmetric-al/core is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add asymmetric-al/core/openspec-update-change@v1.0Pins v1.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- asymmetric-al/core
- Path
.agents/skills/openspec-update-change/SKILL.md- Versions recorded
- 5
- Latest version
- v1.0, committed Oct 21, 2026
- First version recorded
- Aug 18, 2026
- Size
- 10,878 bytes
- Repository stars
- 379
- License
- AGPL-3.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. Also use when the user says "openspec update change" or "opsx update". Requests for the openspec update CLI must use Core's repository-safe refresh workflow; never run the updater against this customized checkout. 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
<!-- CORE-OVERLAY-START --> ## This repository (Asymmetric-al/core) These repo-owned sections sit above the official OpenSpec skill. Reconcile this overlay after upstream refreshes before running `bun run skills:sync`. Use the locally pinned CLI only: `bun run openspec -- <command>`. Do not invoke `@latest`. Core does not use Stores. Pass an explicit change ID before any mutating OpenSpec operation. Follow `AGENTS.md` and `docs/ai/rules/openspec.md`. Do not bypass TDD, exact `base-maia`, data-access boundaries, security, or repository checks. Do not archive unmerged or incomplete work. Do not run `openspec update` against the live customized repository. Do not treat product runtime Eve as a coding agent. Allowed-tools metadata includes `Bash(bun:*)` so the local wrapper can run. ### Triggers - The matching OpenSpec workflow is requested: Explore, Propose, Update, Apply, Verify, Sync, or Archive. - Numbered commands `/1-start-project` through `/4-close-project` wrap these workflows. ### Workflow 1. Read `openspec/config.yaml`, `openspec/project.md`, and the relevant specs or active change. 2. Invoke `bun run openspec --` with the explicit change ID for mutating work. …
Read the whole file at its exact version.
How to install
mdr add asymmetric-al/core/openspec-update-change@sha256:ee7b8c94c13422ebThe line at the top of this page pins the label v1.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_wgyiche275kzhfnm)
5 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Aug 18, 2026 and Oct 21, 2026, about one every 16 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0 latest | 2026-10-21 | 2d5c10a | 10,878 B | A | view · diff |
| v1.0 | 2026-10-21 | 19e63d2 | 10,294 B | A | view · diff |
| v1.0 | 2026-10-21 | d06750d | 10,270 B | A | view · diff |
| v1.0 | 2026-10-21 | 6abe1af | 12,863 B | A | view · diff |
| v1.0 | 2026-08-18 | 2861502 | 8,614 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (10878 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
asymmetric-al/core · 379 stars · license AGPL-3.0 · pushed 2026-10-22 · branch develop
API
GET https://markdownregistry.com/api/v1/artifacts/art_wgyiche275kzhfnm GET https://markdownregistry.com/api/v1/resolve?ref=asymmetric-al/core/openspec-update-change GET https://markdownregistry.com/api/v1/blob/ee7b8c94c13422eb126dcc98308bbf25b5bccd87d621f4d6458c3e352afa0ed2
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 asymmetric-al/core
Every file in asymmetric-al/core