bug-review-board SKILL.md skillA
bug-review-board from korallis/agent-stack is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add korallis/agent-stack/bug-review-board@git:20260930.ce1c74bPins git:20260930.ce1c74b in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- korallis/agent-stack
- Path
skills/bug-review-board/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260930.ce1c74b, committed Sep 30, 2026
- Size
- 6,793 bytes
- Repository stars
- 35
- License
- Apache-2.0
Real-user bug hunt on the running app (the Playwright MCP browser for a web app, the public command or HTTP API for CLI and API work), ending in a ship YES/NO verdict. Use when QA checks a PR or a wave before merge, or when someone asks "is this ready to ship?". Files P0/P1/P2 bugs as queue rows to the lead and records the verdict as proof for the merge gate.
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
# Bug review board (BRB) Use the app the way a careful, slightly unforgiving customer would, and write down everything that goes wrong. You do not read the source to decide whether something works. The user never sees the source. ## Before you start 1. Scope: which PR or wave, which head commit, which deployed or local URL. 2. Read what the app promises: `docs/VERIFY.md` (the feature map, see the `verification-guide` skill), the slice SPEC and acceptance criteria, `docs/PLAN.md`. Read what just changed: the PR description and diff summary. 3. Read the open bugs for this area (queue rows tagged `bug`). Re-test those first: regressions are the most valuable finds. 4. Test accounts come from `~/.config/agent-stack/secrets/playwright.env` and are typed BY NAME through the Playwright MCP's `--secrets`. For CLI and API work, the app or your command reads credentials from env by name. Never type, paste or echo a credential value into a tool input, a queue row, a PR or a proof. If a login you need is missing, ask the lead; don't guess. ## Run the pass Use the interface a user of this feature uses, with the steps in `docs/VERIFY.md`: …
Read the whole file at its exact version.
How to install
mdr add korallis/agent-stack/bug-review-board@sha256:c6b780d3f2549482The line at the top of this page pins the label git:20260930.ce1c74b, 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_5ft2crbi2d4y56xv)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Sep 30, 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 (6793 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
korallis/agent-stack · 35 stars · license Apache-2.0 · pushed 2026-10-05 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_5ft2crbi2d4y56xv GET https://markdownregistry.com/api/v1/resolve?ref=korallis/agent-stack/bug-review-board GET https://markdownregistry.com/api/v1/blob/c6b780d3f2549482523492a32fb8b55fd1f96b72e1e7fd555ac6e4c11afd733d
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.