worca-release SKILL.md skillA
worca-release from sinishadjukic/worca-cc is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add sinishadjukic/worca-cc/worca-release@git:20261001.12dcf23Pins git:20261001.12dcf23 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- sinishadjukic/worca-cc
- Path
.claude/skills/worca-release/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261001.12dcf23, committed Oct 1, 2026
- First version recorded
- Aug 19, 2026
- Size
- 15,803 bytes
- Repository stars
- 43
- License
- MIT
Cut a release candidate or a stable release of @worca/app — bumps the version, commits, tags `worca-app-v<version>`, and pushes so CI publishes to npm with provenance — and, with --publish-changelog, commit a /worca-changelog entry to dev and put it on docs.worca.dev. Triggers on "cut a release", "cut an RC", "release candidate", "bump RC", "stable release", "worca-release", "publish the changelog", or any request to release @worca/app.
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
# Release @worca/app The git tag is the trigger and the source of truth. You bump the version, tag it, and push; `.github/workflows/release-npm-app.yml` validates, tests, and publishes with an OIDC provenance attestation. **Never run `npm publish` by hand** — a manual publish burns the version number and produces an unattested tarball. The rules behind this procedure live in `docs/RELEASING.md`. Read it when something here doesn't fit; do not restate its contents back to the user. **Usage:** - `/worca-release` — print status and stop - `/worca-release --rc` — cut the next release candidate - `/worca-release --stable` — close out the current RC line - `/worca-release --version:micro` — stable release from stable, patch bump - `/worca-release --version:minor` — stable release from stable, minor bump - `/worca-release --publish-changelog` — commit the changelog entry `/worca-changelog` left in `docs/changelog/`, push it to `dev`, and put it on docs.worca.dev (see *Changelog mode* at the end). Add `--version:<V>` to name the entry; the default is the newest one in `entries.json`. It does not cut a release and does not combine with `--rc` / `--stable`. …
Read the whole file at its exact version.
How to install
mdr add sinishadjukic/worca-cc/worca-release@sha256:195846380f49e21eThe line at the top of this page pins the label git:20261001.12dcf23, 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_w554jmcpqjt237fl)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Aug 19, 2026 and Oct 1, 2026, about one every 11 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261001.12dcf23 latest | 2026-10-01 | 12dcf23 | 15,803 B | A | view · diff |
| git:20260929.ca08cdf | 2026-09-29 | ca08cdf | 14,286 B | A | view · diff |
| git:20260929.4b792eb | 2026-09-29 | 4b792eb | 10,579 B | A | view · diff |
| git:20260819.a4bf0af | 2026-08-19 | a4bf0af | 10,345 B | A | view · diff |
| git:20260819.f77c25a | 2026-08-19 | f77c25a | 10,271 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 (15803 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
sinishadjukic/worca-cc · 43 stars · license MIT · pushed 2026-10-22 · branch dev
API
GET https://markdownregistry.com/api/v1/artifacts/art_w554jmcpqjt237fl GET https://markdownregistry.com/api/v1/resolve?ref=sinishadjukic/worca-cc/worca-release GET https://markdownregistry.com/api/v1/blob/195846380f49e21e629ea98a67a504a5cb99d5809bdbc73d5f3741fc504042c1
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.