release-qa SKILL.md skillA
release-qa 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/release-qa@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/release-qa/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261026.505a1da, committed Oct 26, 2026
- First version recorded
- Oct 26, 2026
- Size
- 8,288 bytes
- Repository stars
- 30
- License
- MIT
QA an epic before release on the local environment. Check the environment without changing it, run the browser e2e suite and sort every failure, do exploratory testing in a real browser, file reproduced bugs in the tracker, and give a release call. Use when the user asks for release QA, a bug-hunting pass, or "is this epic ready to release".
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
# Release QA You are QA for one epic. Find out whether "ready for release" is true, and file what isn't. Don't fix anything: no edits to app or test code, no status changes on existing tickets. **First, load the team config with `roost-config`.** You run in the session of the repo that holds the e2e suite (the one with `e2e` in `repos`). **No app to QA in a browser?** When the config has no `stack`, or no repo with `e2e` (a plugin or a library, say), steps 1 to 3 don't apply. You run in the lead repo's session (`planning.lead_repo`) instead, and QA is: 1. **Every repo's own checks** on the epic's newest code (its newest branches or open PRs, merged or not; the same commits for all three checks), as each repo's `tests` says (for this plugin, for example, `claude plugin validate --strict .` and its scripts' checks). 2. **The epic's tests,** run the way the tests adapter says (for `tests.kind: evals`, every case linked to the epic's stories), and sorted as step 2 sorts failures. 3. **Each story's acceptance criteria,** checked against what that same code actually does, one row per criterion with its evidence. …
Read the whole file at its exact version.
How to install
mdr add beakpoint-insights/roost/release-qa@sha256:cb7e703a694a4db4The 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_5zyadak7ewsr7ee2)
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 | 8,288 B | A | view · diff |
| git:20261026.66cdcd9 | 2026-10-26 | 66cdcd9 | 7,083 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 (8288 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_5zyadak7ewsr7ee2 GET https://markdownregistry.com/api/v1/resolve?ref=beakpoint-insights/roost/release-qa GET https://markdownregistry.com/api/v1/blob/cb7e703a694a4db4c303e998811d7df2e5d601f41906d51b7bc0c74d70aad815
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.
More from beakpoint-insights/roost
Every file in beakpoint-insights/roost