pre-release-review 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.
pre-release-review from gtapps/hermitd is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add gtapps/hermitd/pre-release-review@git:20261002.2f2da1bPins git:20261002.2f2da1b in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- gtapps/hermitd
- Path
.claude/skills/pre-release-review/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261002.2f2da1b, committed Oct 2, 2026
- First version recorded
- Jul 23, 2026
- Size
- 17,398 bytes
- Repository stars
- 82
- License
- MIT
Pre-release gate for the monorepo — establishes per-plugin release boundaries (each plugin's last tag → HEAD), audits every changed plugin's CHANGELOG against the actual code diff, and, depending on the objective the operator picks up front, either hands off to the native `/code-review high --fix` for the deep correctness pass or runs an adversarial design review of what shipped (overengineering, alternative designs, downstream-hermit impact) sourced from the PRs, issues, and proposals behind…
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
# Pre-Release Review The gate you run right before `/release <slug>` or `/fleet-release`. It answers two questions the release skills assume are already true: 1. **What is actually shipping?** — the real per-plugin diff since each plugin's last tag, not what you think you changed. 2. **Do the changelogs tell the truth about it?** — every operator-visible change has a CHANGELOG line, and no line over- or under-states what the code does. Then, depending on the mode picked in Step 0, it either runs the native `/code-review high --fix` as the deep correctness pass over the release window, or an adversarial design review of what shipped (Step 3D). This is a **read-only audit** for its own steps — it never bumps a version, writes a changelog, commits, or tags. `/code-review --fix` (step 4) is the one part that mutates the working tree, and only to apply review fixes. Releasing stays the operator's explicit call via `/release`. ## Usage `/pre-release-review [<plugin-slug>...] [<objective>]` - **No slug** — sweep every plugin under `plugins/*/` that has commits since its own last tag. This is the default and the common case. …
Read the whole file at its exact version.
How to install
mdr add gtapps/hermitd/pre-release-review@sha256:bbf8d78f804910e8The line at the top of this page pins the label git:20261002.2f2da1b, 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_m5h2alvk7voxv7pb)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Jul 23, 2026 and Oct 2, 2026, about one every 18 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261002.2f2da1b latest | 2026-10-02 | 2f2da1b | 17,398 B | A | view · diff |
| git:20260913.3363616 | 2026-09-13 | 3363616 | 17,429 B | A | view · diff |
| git:20260902.0f820d6 | 2026-09-02 | 0f820d6 | 17,443 B | A | view · diff |
| git:20260828.ec7f422 | 2026-08-28 | ec7f422 | 17,427 B | A | view · diff |
| git:20260723.8bd6c1a | 2026-07-23 | 8bd6c1a | 13,079 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 (17398 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
gtapps/hermitd · 82 stars · license MIT · pushed 2026-10-22 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_m5h2alvk7voxv7pb GET https://markdownregistry.com/api/v1/resolve?ref=gtapps/hermitd/pre-release-review GET https://markdownregistry.com/api/v1/blob/bbf8d78f804910e86c0d9e1a2f65831a93287aacca41a086bcce203a932eec10
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.