vt-c-bug-report¶
Report a bug — creates a BugChen intake file (BUG-NNN.md) in intake/pending/bugs/
Plugin: core-standards
Category: Other
Command: /vt-c-bug-report
/vt-c-bug-report — Bug Intake Skill¶
Create a structured bug report in the intake pipeline. Asks clarifying questions and writes a BUG-NNN.md file to intake/pending/bugs/ for later triage.
Invocation¶
/vt-c-bug-report # Start with no context
/vt-c-bug-report "login fails on Safari" # Start with initial description
Execution¶
Step 1: Parse Argument¶
If an argument was provided, use it as the initial bug description. If no argument, set initial description to empty string.
Step 2: Detect Branch Context¶
Run: git branch --show-current
Extract related spec or bug:
- If branch matches feature/spec-NNN-*: related_spec = SPEC-NNN
- If branch matches fix/bug-NNN-*: related_bug = BUG-NNN
- Otherwise: no related context
Step 3: Ask Structured Questions¶
Use AskUserQuestion to collect:
-
Bug description (if not provided as argument): "What is the bug? Describe what happens."
-
Severity: "What is the severity?" Options: critical (system down / data loss), high (major feature broken), medium (feature partially broken), low (minor issue / cosmetic)
-
Steps to reproduce: "What are the steps to reproduce? (e.g. 1. Go to login page, 2. Enter email, 3. Click submit)"
-
Expected behavior: "What should happen?"
-
Actual behavior: "What actually happens?"
-
Screenshots or logs (optional): "Any screenshot paths or log snippets? (press Enter to skip)"
Step 4: Auto-Increment BUG Number¶
Scan for the highest existing BUG number:
1. Glob intake/pending/bugs/BUG-*.md → extract NNN from each filename
2. Glob bugs/*/report.md → read YAML frontmatter id: from each
Take the maximum found. Next BUG number = max + 1 (pad to 3 digits: BUG-001, BUG-002, ...). If no existing bugs found, start at BUG-001.
Step 5: Write BugChen File¶
Write to intake/pending/bugs/BUG-NNN.md:
---
id: BUG-NNN
title: [first 60 chars of description]
severity: [critical|high|medium|low]
status: reported
reporter: user
reported_at: [ISO-8601 date]
branch: [current branch name]
related_spec: [SPEC-NNN or null]
related_bug: [BUG-NNN or null]
screenshots: [list of paths, or []]
---
# BUG-NNN: [description]
## Severity
[severity]
## Steps to Reproduce
[steps]
## Expected Behavior
[expected]
## Actual Behavior
[actual]
## Screenshots / Logs
[screenshots or "None provided"]
Step 6: Confirm¶
Display: