release-sync skillA
release-sync is agent-read markdown (skill) from legeling/prompthub: PromptHub release update skill. Use for `/update-readme`, version bumps, changelog updates, website sync, GUI screenshot/doc refresh, and multilingual release/documentation alignment..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified before it reaches your agent: the main file against the SHA-256 recorded here, the others against the git hashes of its source commit. The deterministic audit below grades the latest version, and the same checks always give the same file the same grade.
What the file says
# PromptHub Release Sync Use this skill for version bumps, release preparation, changelog or README updates, website release sync, screenshots, and multilingual release material. ## Read First 1. `AGENTS.md` 2. `spec/releases/release-rules.md` 3. `spec/releases/README.md` and the target version record, when present 4. `package.json`, workspace package manifests, and the newest relevant `CHANGELOG.md` section Do not treat this skill as a second release-policy source. Stable release semantics belong in `spec/releases/release-rules.md`; this skill is the execution procedure. ## Establish Scope Before editing, identify: - target version and release date - stable, prerelease, historical prerelease, or docs-only update - affected distributions: desktop, CLI, self-hosted web, worker, mobile - whether public copy, in-app copy, screenshots, installers, or signing changed For non-trivial release work, create or update the matching active change before implementation. ## Source And Sync Order 1. Update version-bearing manifests for affected distributions, including the root and workspace packages when the monorepo version changes. …
Read the whole file at its exact version.
How to install
mdr add legeling/prompthub/release-sync@git:20260710.7ab8f7fmdr add legeling/prompthub/release-sync@sha256:992a86de1a862019Pin to a label to follow the author's releases, or to a sha256 for exact bytes. Either way the resolved hash is written to mdr.lock, and mdr install fetches those bytes again and checks them, so it installs them exactly or fails.
[](https://markdownregistry.com/a/art_vjwxypp7ev3nzzt6)
0 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260710.7ab8f7f latest | 2026-07-10 | 7ab8f7f | 3,911 B | A | view · diff |
| git:20260407.2dadd0c | 2026-04-07 | 2dadd0c | 3,888 B | A | view · diff |
| git:20260319.9e1f6a4 | 2026-03-19 | 9e1f6a4 | 3,038 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 (3911 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
legeling/prompthub · 1,675 stars · license AGPL-3.0 · pushed 2026-09-28 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_vjwxypp7ev3nzzt6 GET https://markdownregistry.com/api/v1/resolve?ref=legeling/prompthub/release-sync GET https://markdownregistry.com/api/v1/blob/992a86de1a862019068fa7b138cf86eab87b400bd9874ab62ff0140b6d394922
Your agent 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.
More from legeling/prompthub
Every file in legeling/prompthub