bug-report

스타8

포크0

업데이트2026년 4월 15일 20:51

Structured bug report creation with repro steps, expected/actual behavior, and severity classification.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

출처

CodePhobiia

CodePhobiia/claude-roblox-game-studio

GitHub 저장소 열기 Creator 저장소 보기

다운로드

/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-<date>-<NNN>.md
Add to production/bugs/index.md if that exists
For S0/S1: Immediately escalate to qa-lead + producer
Delegate investigation to the appropriate specialist based on affected system

이 저장소의 다른 Skills

같은 저장소

doctor

CodePhobiia/claude-roblox-game-studio

Run a comprehensive health check on the repo. Verifies README counts match reality, promised files exist, no unresolved placeholders, wiki index is synced, toolchain configs are valid, and agent roster is accurate. Use after making structural changes or before publishing.

2026-04-168

start

CodePhobiia/claude-roblox-game-studio

Begin a new Roblox game project or onboard to an existing one. Use when starting a fresh session with no context, or when the user says "let's start" or "new project".

2026-04-168

asset-from-image

CodePhobiia/claude-roblox-game-studio

Generate a 3D asset from a reference image using Blender MCP's image-to-3D AI (Hyper3D). Optimizes for Roblox and exports FBX.

2026-04-168

generate-asset

CodePhobiia/claude-roblox-game-studio

Generate a 3D asset for Roblox using Blender MCP. Creates models from text descriptions via AI (Hyper3D/Hunyuan3D) or downloads from PolyHaven/Sketchfab, optimizes for Roblox constraints, and exports FBX.

2026-04-168

studio-inspect

CodePhobiia/claude-roblox-game-studio

Inspect the current Roblox Studio state via MCP. Verifies instance hierarchy, checks for common structural issues, and reports findings.

2026-04-168

studio-screenshot

CodePhobiia/claude-roblox-game-studio

Capture a screenshot of the current Roblox Studio viewport and analyze it. Use for visual verification of UI, lighting, level layout, and general game appearance.

2026-04-168

/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-<date>-<NNN>.md

Add to production/bugs/index.md if that exists

For S0/S1: Immediately escalate to qa-lead + producer

Delegate investigation to the appropriate specialist based on affected system

name	bug-report
description	Structured bug report creation with repro steps, expected/actual behavior, and severity classification.