running-bug-review-board
Runs real-user QA, manual test plans, UX bug hunts, build sign-off, bug filing, and bug triage for web or iOS/iPadOS apps. Use when asked "QA this", "is this ready to ship?", or similar. Produces P0/P1/P2 bug reports, YES/NO phase sign-off, tracker sync guidance, and an HTML QA dashboard; keeps Interactive BRB triage in a separate session.
npx skills add RayFernando1337/rayfernando-skills --skill running-bug-review-board --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Running the Bug Review Board (BRB) QA pass This skill runs a **real-user QA pass** on an app and feeds the output into a Bug Review Board: a folder of structured bug reports, per-pass run reports, a self-contained HTML dashboard, and a final YES/NO sign-off the team can act on. Engineering's tracker (Linear / GitHub / Jira / Notion) syncs bi-directionally so QA and engineering stay in step. It generalizes a battle-tested workflow that already shipped phase QA on Mokuhoe — the techniques are repo-agnostic. ## Why this exists Most engineers test their own code. They confirm what they wrote works. That misses the bugs **real users hit first** — stale state across flows, mobile overflow, copy that lies, paths that 404 mid-onboarding, race conditions between auth and routing. This skill simulates a real user. The QA agent acts like a careful, mildly unforgiving customer who does not read the source code. ## Two workflows — Auto QA and Interactive BRB The skill splits the work into two distinct modes that share artifacts but **run in separate sessions** on purpose: - **Auto QA pass** — the agent drives the app, runs scenarios, files bugs, generates the HTML report, writes a verdict. Op
- Why this exists
- Two workflows — Auto QA and Interactive BRB
- The trifecta — three hats, one pass
- Discover the app first (or you'll write bad tests)
- Workflow (any phase, any repo)
- Mode picker
- Surfaces — which playbook activates
- Issue tracker integration
- HTML report (Zite + Dieter Rams)
- Pattern-based triage suggestions
- Scaffold folders if missing
- Always
- Never
- Bug priority (BRB taxonomy)
bash <skill>/scripts/scaffold-qa.sh "$REPO_ROOT" PHASE_NUM [SLUG]
What does the running-bug-review-board skill do?
Runs real-user QA, manual test plans, UX bug hunts, build sign-off, bug filing, and bug triage for web or iOS/iPadOS apps. Use when asked "QA this", "is this ready to ship?", or similar. Produces P0/P1/P2 bug reports, YES/NO phase sign-off, tracker sync guidance, and an HTML QA dashboard; keeps Interactive BRB triage in a separate session.
How do I install it?
Run `npx skills add RayFernando1337/rayfernando-skills --skill running-bug-review-board --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From RayFernando1337/rayfernando-skills, a repository with 117 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.