review-epic SKILL.md skillA
review-epic from beakpoint-insights/roost is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add beakpoint-insights/roost/review-epic@git:20261026.505a1daPins git:20261026.505a1da in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- beakpoint-insights/roost
- Path
skills/review-epic/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261026.505a1da, committed Oct 26, 2026
- First version recorded
- Oct 26, 2026
- Size
- 4,680 bytes
- Repository stars
- 30
- License
- MIT
Review a whole epic's code before it's released, in every repo it touches, against main. Each repo's session runs /code-review at high effort on everything the epic's stack changes, and the lead repo's session also runs /security-review, looking for what slice-by-slice reviews miss (how the slices interact, fixes layered on fixes, code that was never reviewed). Findings come back to one checkpoint for the user's decisions (fix now, ticket for later, skip), then go to the owning session. Use…
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 Epic Slice reviews look at one slice against the slice below it, and bug fixes added after a slice's review often get none. Nothing looks at the epic as a whole, the way it will merge. This skill does, once, before release. Talk to the repo sessions exactly as `run-slice` describes. You never review, edit or test any repo yourself. **First, load the team config with `roost-config`.** ## Inputs - **EPIC:** the epic's ticket key. ## 1. Know what was and wasn't reviewed List every PR on the epic's stacks in every repo (the epic's **Release order** comment, or `gh stack`), and for each, how it was reviewed: - GitHub reviews (`gh pr view <n> --json reviews`): Copilot, the Claude app, people; - `/code-review` runs recorded in run-slice's state files (`<team.state_dir>/STORY.md`) or the stories' `run-slice checkpoint:` comments; - none. Mark the PRs that were never reviewed, and fixes made after a slice's review. The sessions should look hardest there. ## 2. Ask for the reviews Send each session one message (they can all run at once): …
Read the whole file at its exact version.
How to install
mdr add beakpoint-insights/roost/review-epic@sha256:35304cb0bebd94d8The line at the top of this page pins the label git:20261026.505a1da, 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_pkqjc3xdy5mj77er)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, all committed on Oct 26, 2026.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261026.505a1da latest | 2026-10-26 | 505a1da | 4,680 B | A | view · diff |
| git:20261026.66cdcd9 | 2026-10-26 | 66cdcd9 | 4,476 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 (4680 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
beakpoint-insights/roost · 30 stars · license MIT · pushed 2026-10-31 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_pkqjc3xdy5mj77er GET https://markdownregistry.com/api/v1/resolve?ref=beakpoint-insights/roost/review-epic GET https://markdownregistry.com/api/v1/blob/35304cb0bebd94d8715e68b3e5e259bff65fbdd0129b2ca8e63b332b16650f11
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.