Bug Report
Structured bug report creation with repro steps, expected/actual behavior, and severity classification.
Install
$ agentstack add skill-codephobiia-claude-roblox-game-studio-bug-report ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-codephobiia-claude-roblox-game-studio-bug-report) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
/bug-report — Bug Report Creation
Delegate to: qa-tester (with qa-lead for triage)
Steps
1. Gather Information
Ask the user for:
- Short description: One sentence summary
- What happened: What did you observe?
- What should have happened: Expected behavior
- When: Did this just start or has it been happening?
- Where: Which system/feature is affected?
- Device: Platform (mobile/PC/console), screen size, network
- Frequency: Always / sometimes / once?
- Impact: How many players affected? Data loss risk?
2. Reproduce (if possible)
Work with the user to find reliable repro steps:
- Start from a known state (e.g., fresh login)
- List each action taken
- Note the exact point where behavior diverges from expected
3. Classify Severity
- S0 — Critical: Data loss, crashes, security exploits, can't play
- S1 — Major: Feature broken for many users, major visual/UX issues
- S2 — Normal: Feature works but with noticeable problems
- S3 — Minor: Small glitches, edge cases, polish items
- S4 — Cosmetic: Typos, minor style issues
4. Generate Bug Report
Use .claude/docs/templates/bug-report-template.md as the base.
# BUG: [Short descriptive title]
**ID**: BUG-YYYY-MM-DD-NNN
**Severity**: [S0-S4]
**Device**: [Platform, resolution, network]
**Build**: [Version or git commit]
**Reported**: YYYY-MM-DD
**Status**: Open
## Steps to Reproduce
1. [Step 1]
2. [Step 2]
3. [Step 3]
## Expected Behavior
[What should happen]
## Actual Behavior
[What actually happens]
## Evidence
- Screenshots: [paths or links]
- Video: [link if available]
- Console output: [paste relevant errors]
- Stack trace: [paste if available]
## Affected Systems
- [System 1]
- [System 2]
## Suspected Root Cause
[Any theories about where the bug lives]
## Workaround (if known)
[Anything the user can do to avoid it]
## Notes
[Anything else relevant]5. Save and Triage
Present the report to the user. On approval:
- Save to
production/bugs/BUG--.md - Add to
production/bugs/index.mdif that exists - For S0/S1: Immediately escalate to qa-lead + producer
- Delegate investigation to the appropriate specialist based on affected system
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: CodePhobiia
- Source: CodePhobiia/claude-roblox-game-studio
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.