Running Bug Review Board
Runs a real-user manual QA pass against any web/mobile/desktop app and turns the results into a Bug Review Board (BRB) feedback loop. Use whenever the user says "QA this", "test phase N", "run a manual test plan", "act as a real user", "find UX bugs", "sign off this build", "file a bug report", or "is this ready to ship?" — even if they only describe the symptoms ("the signup flow feels broken", "check what's wrong before we move on", "we finished feature X"). Drives the trifecta: PM (verifies user-promise), QA (executes scenarios from a real user's perspective), and Engineer (flags invalidated assumptions). Repo-agnostic, browser-tool-agnostic, scaffolds folders for bug reports + run reports + coordinator merges with P0/P1/P2 priorities. Works alongside cursor-ide-browser, browser-use, Playwright, manual driving, or any future browser tool.
Security AStatic scan found no risk patternsHow grading works ›
From the source SKILL.md
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, and a final YES/NO sign-off the team can act on. It generalizes a battle-tested workflow that already shipped phase QA on Mokuhoe — the techniques are repo-agnostic.
What this skill does
Running Bug Review Board is a community-contributed Claude Code skill in the scaffolders sub-category. It ships as a SKILL.md file that Claude Code auto-discovers under ~/.claude/skills/running-bug-review-board/ and loads when your prompt matches the skill's trigger.
When to invoke it: Use whenever the user says "QA this", "test phase N", "run a manual test plan", "act as a real user", "find UX bugs", "sign off this build", "file a bug report", or "is this ready to ship?" — even if they only describe the symptoms ("the signup flow feels broken", "check what's wrong before we move on", "we finished feature X"). Drives the trifecta: PM (verifies user-promise), QA (executes scenarios from a real user's perspective), and Engineer (flags invalidated assumptions).
Who uses this skill
The Running Bug Review Board Claude Code skill is built for developers, power users, and teams automating repetitive workflows and improving developer experience. It's part of ClaudSkills (also referred to as Claude Skills or Claude Code Skills) — the open community-curated registry of 153,000+ SKILL.md files for Anthropic's Claude Code agent and the wider Claude ecosystem (Claude API, Claude Agent SDK).
How to install
Free
Manual install (2 steps)
mkdir -p ~/.claude/skills/running-bug-review-board
curl -L https://claudskills.com/skills/running-bug-review-board/SKILL.md \
-o ~/.claude/skills/running-bug-review-board/SKILL.md
Or just download SKILL.md directly and drop it into ~/.claude/skills/running-bug-review-board/. Claude Code auto-discovers it on next session.
Skills live at ~/.claude/skills/running-bug-review-board/SKILL.md on macOS/Linux, or %USERPROFILE%\.claude\skills\running-bug-review-board\SKILL.md on Windows. See the full install guide for step-by-step instructions.
Telegram
📱 Install from your phone or desktop Telegram
Open @claudskills_bot on Telegram, tap Open Desktop App, and the desktop app installs this skill for you. Or share the bot link with a colleague — they get the same one-tap install. Learn more →
Pro
One-click install via the desktop app
The ClaudSkills desktop app installs any skill directly into ~/.claude/skills/ with one click — no terminal required. Pro starts at $9/mo or $149 lifetime.
Pro
For the full experience including quality scoring and one-click install features for each skill — upgrade to Pro.
Frequently asked questions
How do I install the Running Bug Review Board Claude Code skill?
Install via the ClaudSkills desktop app (one click) or copy
SKILL.md from the source repository to
~/.claude/skills/running-bug-review-board/SKILL.md and restart Claude Code. Both flows are detailed at
claudskills.com/install/.
What does the Running Bug Review Board skill do?
Runs a real-user manual QA pass against any web/mobile/desktop app and turns the results into a Bug Review Board (BRB) feedback loop. Use whenever the user says "QA this", "test phase N", "run a manual test plan", "act as a real user", "find UX bugs", "sign off this build", "file a bug report", or "is this ready to ship?" — even if they only describe the symptoms ("the signup flow feels broken", "check what's wrong before we move on", "we finished feature X"). Drives the trifecta: PM (verifies user-promise), QA (executes scenarios from a real user's perspective), and Engineer (flags invalidated assumptions). Repo-agnostic, browser-tool-agnostic, scaffolds folders for bug reports + run reports + coordinator merges with P0/P1/P2 priorities. Works alongside cursor-ide-browser, browser-use, Playwright, manual driving, or any future browser tool.
Is this skill free to install?
Yes. ClaudSkills is an open registry — every skill keeps its source repository's license, and manual install via copy is free. ClaudSkills Pro ($9/mo, $79/yr, or $149 one-time) adds one-click install via the desktop app and a multi-signal Quality Score.
When should I use the Running Bug Review Board skill?
Use Running Bug Review Board when your Claude Code task falls under the Dev Tools category — specifically in the scaffolders area. Claude Code auto-discovers installed skills and invokes the right one based on the task description, so you can also ask Claude directly (e.g. "use Running Bug Review Board" or describe the task and let Claude pick). Browse related skills at
/category/tools/.
What is a Claude Code skill and how does the Running Bug Review Board skill fit in?
A Claude Code skill is a
SKILL.md file that lives under
~/.claude/skills/<name>/ and tells the Claude Code CLI agent how to perform a specific task (instructions, prompts, allowed tools). Skills are auto-discovered at session start. Running Bug Review Board is one of 67,000+ skills indexed in the open ClaudSkills catalog, classified under the Dev Tools category. Learn more at
/learn/what-is-a-claude-skill/.
Attribution & license
Cite this skill
If you reference this skill in a blog post, paper, or documentation, you can cite it as:
APA
RayFernando1337. (2026). Running Bug Review Board [Claude Code skill]. ClaudSkills. https://claudskills.com/skills/running-bug-review-board/
BibTeX
@misc{running-bug-review-board-2026,
author = {RayFernando1337},
title = {Running Bug Review Board [Claude Code skill]},
year = {2026},
publisher = {ClaudSkills},
url = {https://claudskills.com/skills/running-bug-review-board/}
}
Embed this skill
Promote, attribute, or link this skill from your own README, blog post, or documentation. All three snippets are free to use — no sign-up, no API key. More distribution surfaces →
Badge
[](https://claudskills.com/skills/running-bug-review-board/?utm_source=badge&utm_medium=readme&utm_campaign=skill_badge)
<script>
<script src="https://claudskills.com/embed/running-bug-review-board.js" async></script>
<iframe>
<iframe src="https://claudskills.com/embed/running-bug-review-board.html" width="100%" height="160" frameborder="0" loading="lazy" title="ClaudSkills: Running Bug Review Board"></iframe>
Security scan
Grade A · scanned 2026-07-18 — free static scan against the OWASP Agentic Skills Top 10.
No risk patterns were found in any of the ten OWASP-aligned categories. How grading works ›
- ✓ Prompt injection
- ✓ Data exfiltration
- ✓ Supply chain
- ✓ Reverse shell
- ✓ Credentials
- ✓ Execution
- ✓ Filesystem
- ✓ Persistence
- ✓ Obfuscation
- ✓ Network
Show this grade on your repo (click to copy):
[](https://claudskills.com/skills/running-bug-review-board/#security)
More Dev Tools skills
Browse all Dev Tools skills in the ClaudSkills registry, or explore these other picks from the same category:
Part of Acreator Store — Adam Lankamer's AI tools:
PerfectStudio ·
Ucaption ·
UTagger ·
AutoXPoster ·
TestYourSkills ·
AutomationFlows ·
Au Naturel ·
Telegram @acreatorstore