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
.agents/skills/pre-release-review/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261002.2f2da1b, committed Oct 2, 2026
- First version recorded
- Jul 25, 2026
- Size
- 13,314 bytes
- Repository stars
- 82
- License
- MIT
Run the pre-release gate for this multi-plugin monorepo: establish each plugin's release boundary from its last reachable tag to HEAD, audit every changed plugin's [Unreleased] changelog against the actual code diff, identify contract-surface and breaking changes, and, per the objective the user picks up front, either run a dedicated Codex correctness review over the exact union release window or an adversarial design review of what shipped…
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
Run this gate immediately before `$release` or `$fleet-release`. Answer:
1. What is actually shipping in each plugin?
2. Does each plugin's `[Unreleased]` changelog accurately describe that diff?
3. Per the mode picked in Step 0: does a dedicated Codex review find correctness problems in the union release window (Step 4), or is what shipped the right design for a downstream hermit (Step 3D)?
Keep Steps 1–3 and 3D read-only. Do not edit changelogs, bump versions, commit, tag, or push. Step 4 may edit only when the user chose the disclosed review-and-fix mode in Step 0.
## Invocation
- `$pre-release-review` — audit every plugin with commits since its own last tag.
- `$pre-release-review` for one or more `<plugin-slug>`s — audit only those plugins.
- Any trailing free text is the objective: it settles the Step 0 mode when it clearly names one ("design review", "run the deep pass too") and otherwise becomes the lens the verdict answers.
When installed, `$release-status` is an optional lightweight precursor. `$docs-drift` is the documentation follow-up after this changelog-vs-code audit.
## Step 0 — Pick the mode
…Read the whole file at its exact version.
How to install
mdr add gtapps/hermitd/pre-release-review@sha256:f87c71a63e10ded1The 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_ejmkkvnygw6ojq6f)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Jul 25, 2026 and Oct 2, 2026, about one every 23 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261002.2f2da1b latest | 2026-10-02 | 2f2da1b | 13,314 B | A | view · diff |
| git:20260905.0c707c7 | 2026-09-05 | 0c707c7 | 13,336 B | A | view · diff |
| git:20260828.ec7f422 | 2026-08-28 | ec7f422 | 13,308 B | A | view · diff |
| git:20260725.57c2b3a | 2026-07-25 | 57c2b3a | 8,883 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 (13314 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_ejmkkvnygw6ojq6f GET https://markdownregistry.com/api/v1/resolve?ref=gtapps/hermitd/pre-release-review GET https://markdownregistry.com/api/v1/blob/f87c71a63e10ded12809ad71d425a2d8c7c0f36fe6b0db92247ddd79c3b90b6a
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.