Language: Always interact with the user in 日本語.
bug-report-en
Usable by non-engineers. Just answer questions to create a proper bug report.
Prerequisites
- Claude Code environment
gh CLI (for GitHub Issue output)
Arguments
- Text (e.g.,
/bug-report-en Can't log in): Use as initial info, interview for missing details
- No arguments: Start interviewing from scratch
Phase 1: Interview
Ask in plain language without technical jargon.
1-1: Basic Information
Use AskUserQuestion to gather (skip what's already known from arguments):
- What happened: What problem occurred
- Where it happened: Which screen, feature, or page
- Error messages: Displayed on screen or console (request screenshots)
1-2: Follow-up Questions
Ask only what's needed based on responses (max 3, don't ask what can be inferred):
| Situation |
What to ask |
| Error message exists |
Error details, screenshots |
| Reproduction unclear |
Every time or specific conditions |
| Screen/UI issue |
Browser, device, screen size |
| Data issue |
Specific data/account only |
| Timing issue |
Since when, recent changes |
| Steps unclear |
Specific operation steps |
Phase 2: Codebase Investigation
- Identify related code — Search by screen/feature name/error message with
Grep/Glob. Use Explore agent for broader investigation if needed
- Estimate cause — Trace from error messages/stack traces. State confidence level (certain / likely / needs investigation)
- Check impact scope — Check other features using same code, related tests
- Attempt reproduction — Only if reproducible via tests or commands. Do not create tests
Phase 3: Duplicate Check
- Search existing Issues with
gh issue list --state open --search "<bug-summary>"
- If similar Issue found -> report to user, confirm whether to comment on existing or create new
Phase 4: Preview and Output Destination
- Create draft from gathered info and investigation results
- Show preview to user (technical content + plain explanation)
- Apply revisions if any
- Confirm output destination with
AskUserQuestion:
- GitHub Issue (recommended)
- Local MD file
Phase 5: Output
GitHub Issue
- Create with
gh issue create, title bug: <summary>, label bug
- Use template from
templates/issue.md
- Report URL to user
Local MD
- Generate
bug-report-<summary-kebab-case>.md
- Report path to user
Severity Criteria
| Severity |
Criteria |
Example |
| Critical |
Service down, data loss, security risk |
Can't log in, data deleted |
| High |
Major feature unusable, no workaround |
Search broken, can't save |
| Medium |
Feature works but inconvenient, workaround exists |
Display broken, slow |
| Low |
Minor, no usage impact |
Typo, color mismatch |
Rules
- No technical jargon in interviews. Mirror user's own terms only
- Minimal questions. Don't ask what can be inferred
- Code investigation must verify against actual code, not guess
- State confidence level honestly for cause estimates
- Always preview and get user approval before creating Issue
- Do not modify code. Output is Issue only
- If fix is needed, suggest
/bug-fix #<issue-number>
1---2name: bug-report-en3description: Interactively gather bug details, investigate code, and create a structured GitHub Issue.4user-invocable: true5---67**Language: Always interact with the user in 日本語.**89# bug-report-en1011Usable by non-engineers. Just answer questions to create a proper bug report.1213## Prerequisites1415- Claude Code environment16- `gh` CLI (for GitHub Issue output)1718## Arguments1920- **Text** (e.g., `/bug-report-en Can't log in`): Use as initial info, interview for missing details21- **No arguments**: Start interviewing from scratch2223## Phase 1: Interview2425**Ask in plain language without technical jargon.**2627#### 1-1: Basic Information2829Use `AskUserQuestion` to gather (skip what's already known from arguments):301. **What happened**: What problem occurred312. **Where it happened**: Which screen, feature, or page323. **Error messages**: Displayed on screen or console (request screenshots)3334#### 1-2: Follow-up Questions3536Ask **only what's needed** based on responses (max 3, don't ask what can be inferred):3738| Situation | What to ask |39|-----------|-------------|40| Error message exists | Error details, screenshots |41| Reproduction unclear | Every time or specific conditions |42| Screen/UI issue | Browser, device, screen size |43| Data issue | Specific data/account only |44| Timing issue | Since when, recent changes |45| Steps unclear | Specific operation steps |4647## Phase 2: Codebase Investigation48491. **Identify related code** — Search by screen/feature name/error message with `Grep`/`Glob`. Use `Explore` agent for broader investigation if needed502. **Estimate cause** — Trace from error messages/stack traces. State confidence level (certain / likely / needs investigation)513. **Check impact scope** — Check other features using same code, related tests524. **Attempt reproduction** — Only if reproducible via tests or commands. Do not create tests5354## Phase 3: Duplicate Check55561. Search existing Issues with `gh issue list --state open --search "<bug-summary>"`572. If similar Issue found -> report to user, confirm whether to comment on existing or create new5859## Phase 4: Preview and Output Destination60611. Create draft from gathered info and investigation results622. Show preview to user (technical content + plain explanation)633. Apply revisions if any644. Confirm output destination with `AskUserQuestion`:65 - **GitHub Issue** (recommended)66 - **Local MD file**6768## Phase 5: Output6970#### GitHub Issue71- Create with `gh issue create`, title `bug: <summary>`, label `bug`72- Use template from `templates/issue.md`73- Report URL to user7475#### Local MD76- Generate `bug-report-<summary-kebab-case>.md`77- Report path to user7879## Severity Criteria8081| Severity | Criteria | Example |82|----------|----------|---------|83| Critical | Service down, data loss, security risk | Can't log in, data deleted |84| High | Major feature unusable, no workaround | Search broken, can't save |85| Medium | Feature works but inconvenient, workaround exists | Display broken, slow |86| Low | Minor, no usage impact | Typo, color mismatch |8788## Rules8990- **No technical jargon** in interviews. Mirror user's own terms only91- **Minimal questions**. Don't ask what can be inferred92- Code investigation must **verify against actual code**, not guess93- State confidence level honestly for cause estimates94- **Always preview and get user approval** before creating Issue95- Do not modify code. Output is Issue only96- If fix is needed, suggest `/bug-fix #<issue-number>`
ousiass