Skip to content
Skills Library
Programming · Analysis

bug-from-user

/bug-from-user

Convert a vague user complaint into a reproducible bug report a solo dev can act on. Use when the user pastes a confusing customer message, says "user says it's broken but I can't repro", "this email makes no sense", or wants to triage a bug report.

Repository
solo-skills ↗
Licence
MIT
Last repository change
01.07.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 01.07.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Convert a vague user complaint into a reproducible bug report a solo dev can act on. Use when the user pastes a confusing customer message, says "user says it's broken but I can't repro", "this email makes no sense", or wants to triage a bug report.

Triggers from the description

user says itt reprothis email makes no sense
Original author description

Convert a vague user complaint into a reproducible bug report a solo dev can act on. Use when the user pastes a confusing customer message, says "user says it's broken but I can't repro", "this email makes no sense", or wants to triage a bug report.

How it works

  1. When to use
  2. When NOT to use
  3. The four-question conversion
  4. Output format
  5. Worked example
  6. Anti-patterns to avoid
  7. 中文版
Original SKILL.md headings · 145 lines, 552 words
SKILL.md preview
---
name: bug-from-user
description: Convert a vague user complaint into a reproducible bug report a solo dev can act on. Use when the user pastes a confusing customer message, says "user says it's broken but I can't repro", "this email makes no sense", or wants to triage a bug report.
---

# Bug from User / 用户反馈转 Bug

## When to use

- A user has reported a problem in **prose** (email, Discord, Twitter DM, support ticket).
- The dev cannot tell from the message:
  - what was expected vs. what actually happened
  - the steps to reproduce
  - whether it's a real bug, user error, or a feature request in disguise
- The dev wants a **GitHub issue** or **internal note** they can later sit down and fix.

## When NOT to use

- The user has already produced a **clean, reproducible report**. Don't re-process it.
- The complaint is **subjective** ("it's slow", "it's ugly") with no measurable claim — that's a UX or perf investigation, not a bug.
- The user is **asking for a feature** (e.g. "can you add X?") — file as feature request, not bug.

## The four-question conversion

For any prose complaint, reduce it to:

1. **Trigger** — what did the user *do* (action, click, command, input)?
2. **Expected** — what did they expect to happen?
3. **Actual** — what actually happened?
4. **Surface** — where did it happen (URL, screen, version, browser, OS)?

If any of the four is missing, **flag it as a follow-up question** rather than guessing.

## Output format

```markdown
### Bug: <one-sentence headline, user-perspective>

**Trigger:**
1. <step>
2. <step>

**Expected:** <what they expected>

**Actual:** <what actually happened>

**Surface:** <version / browser / OS / URL>

**Confidence:** <high | medium | low>
- high: report is self-contained, can repro from this alone
- medium: 1–2 reasonable assumptions made
- low: significant guessing — ask user to confirm

**Follow-ups (if any):**
- <question to ask the user>
```

## Worked example

**Input (raw user email):**
> "hey i tried buying the pro plan tonight and the website just kept loading forever, i refreshed a few times then gave up. using safari on my macbook"

**Output:**
```markdown
### Bug: Pro plan checkout hangs on Safari (macOS)

**Trigger:**
1. Visit pricing page on Safari (macOS).
2. Click "Pro plan" purchase button.
3. Observe checkout flow.

**Expected:** Stripe checkout opens within a few seconds.

**Actual:** Page stays in loading state indefinitely; refresh does not recover.

**Surface:** Safari on macOS. Version of Safari and macOS unknown. Pricing page URL unknown (likely /pricing).

**Confidence:** medium
- Assumed pricing page URL is /pricing.
- Assumed checkout uses Stripe.

**Follow-ups:**
- Which Safari version + macOS version?
- Does Chrome on the same machine reproduce it?
- Browser console errors (if comfortable opening DevTools)?
```

## Anti-patterns to avoid

- **Don't assume severity** — "P0 outage" without evidence is alarmist.
- **Don't guess root cause** in the report — that's the dev's job after reading. The report describes symptoms.
- **Don't promise a fix timeline** — that goes in the reply email, not the bug report.

---

## 中文版

### 何时使用

- 用户用**散文**报了一个问题(邮件、Discord、推特 DM、工单)。
- 看不出:
  - 期望 vs 实际
  - 复现步骤
  - 是真 bug、用户操作问题、还是变相的功能请求

### 何时不使用

- 用户已经写好了**清晰可复现**的报告——别重新加工。
- 抱怨是**主观**的("慢"、"丑"),没有可测指标——那是 UX/性能调研,不是 bug。
- 用户是**要功能**——按 feature request 处理。

### 四问转化法

把任何散文压成 4 个问题:

1. **触发**——用户做了什么动作?
2. **期望**——他们期望发生什么?
3. **实际**——实际发生了什么?
4. **环境**——在哪里发生(URL、屏幕、版本、浏览器、系统)?

任意一项缺失 → **列为待问**,不要猜。

### 输出

```markdown
### Bug: <一句话标题,用户视角>

**触发:**
1. <步骤>
2. <步骤>

**期望:** <…>

**实际:** <…>

**环境:** <…>

**置信度:** <high | medium | low>

**待问:**
- <…>
```

### 反模式

- **不要乱定优先级**——没证据就"P0"是恐慌。
- **不要在报告里猜根因**——根因是开发读完之后的事,报告只描述现象。
- **不要承诺修复时间**——那写在回复邮件里,不写在 bug 单里。

Versions

The database has no other skills named bug-from-user.

Database snapshot: 13.11.2026 · package version aaae0c1578a1 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100bug-report
    Turn a vague complaint, screenshot, error message, Slack thread or client email into a clear, reproducible bug report or GitHub issue - title, steps to reproduce, expected vs actual, environment, evidence, severity and suspected cause. Use when the user says "write a bug…
  • 90huddle-bug
    Use when the AI Manager wants to turn a bug description, a capture, a link or a raw report labeled «needs triage» into a ready Bug Issue.
  • 100e2e-repro
    Turn a bug report into one Playwright E2E test that is red on the bug and green once it is fixed, before anyone touches the code. Use when asked to reproduce a bug, write a regression test for a bug report, or confirm a reported bug is real. Reproduces live in a browser with playwright-cli first.
  • 100github-bug-report-triage
    Use when evaluating whether a bug issue has sufficient detail and identifying missing reporter information. Not for non-bug issues or backlog triage: use github-backlog-triage.
  • 85swe-120-triage-a-bug-report
    Turn a bug report into a reproduced, diagnosed and rated issue without changing any code. Use when a bug is reported, an error appears in logs, or someone asks why something is broken.
  • 90filing-bug-reports
    Generate a standalone bug report that another developer can use to reproduce, investigate, and fix an issue. Use when the user says 'file a bug', 'write a bug report', 'report this issue', or asks to document a defect for handoff.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.