rollout-review SKILL.md skillA
rollout-review from cromford-ai/cromford is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add cromford-ai/cromford/rollout-review@git:20261013.1268b26Pins git:20261013.1268b26 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- cromford-ai/cromford
- Path
orchestrator/skills/rollout-review/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261013.1268b26, committed Oct 13, 2026
- Size
- 1,573 bytes
- Repository stars
- 29
- License
- Apache-2.0
Review a multi-wave rollout ticket before its next wave builds. Checks the previous wave merged, Blocked-by lines match the code, and scope stays inside the plan.
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
# Review a rollout wave A rollout is a master ticket split into waves (`BH-NNNN.1`, `.2`, ...). Each wave is its own ticket. Your job is to say whether the next one may build. ## Steps 1. Read the master ticket, its split notice, and the wave ticket in full, comments included. 2. Check the wave before this one. A wave is buildable only after the one before it MERGED. An open PR is not merged. A green build is not merged. 3. Check every `Blocked-by` and `DEPENDS:` line against the code on main: the files, tables, routes or commands it names must exist there. A dependency that is only on a branch is not met. 4. Compare the wave's plan with the master's "Out of scope" list and with the waves after it. Work that belongs to a later wave is scope creep. 5. If the plan is wrong but fixable, ask for an amendment through the plan amend path (#3955). Say exactly which line changes and why. Do not rewrite the plan yourself. ## Verdicts - `proceed`: the previous wave merged, dependencies are on main, scope matches. - `amend`: it can build once a named line of the plan changes. - `hold`: the previous wave has not merged, or a dependency is missing on main. …
Read the whole file at its exact version.
How to install
mdr add cromford-ai/cromford/rollout-review@sha256:dc9750ec441eedc8The line at the top of this page pins the label git:20261013.1268b26, 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_uzgxtst2wkg5vzu5)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 13, 2026.
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 (1573 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
cromford-ai/cromford · 29 stars · license Apache-2.0 · pushed 2026-11-07 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_uzgxtst2wkg5vzu5 GET https://markdownregistry.com/api/v1/resolve?ref=cromford-ai/cromford/rollout-review GET https://markdownregistry.com/api/v1/blob/dc9750ec441eedc86943d663e5ba74d60910e1e74da4c61141c0d1a6424a9c7b
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.