# Bug Reporting Excellence

Write high-quality bug reports that get fixed quickly.

- Repository: https://github.com/proffesor-for-testing/agentic-qe (521 stars)
- Category: Writing
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add proffesor-for-testing/agentic-qe --skill bug-reporting-excellence -g -a claude-code -y`
Codex: `npx skills add proffesor-for-testing/agentic-qe --skill bug-reporting-excellence -g -a codex -y`
Cursor: `npx skills add proffesor-for-testing/agentic-qe --skill bug-reporting-excellence -g -a cursor -y`
Gemini CLI: `npx skills add proffesor-for-testing/agentic-qe --skill bug-reporting-excellence -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add proffesor-for-testing/agentic-qe`

## Description

Write high-quality bug reports that get fixed quickly. Use when reporting bugs, training teams on bug reporting, or establishing bug report standards.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Bug Reporting Excellence

<default_to_action>
When reporting bugs:
1. TITLE: `[Component] fails [Condition] causing [Impact]`
2. DESCRIBE: Expected behavior → Actual behavior → Steps to reproduce
3. INCLUDE: Environment, severity, screenshots/logs, business impact
4. ISOLATE: Narrow down conditions (browser, user, amount thresholds)
5. ONE BUG = ONE REPORT (don't combine issues)

**Bug Report Formula:**
```markdown
## [Component] Issue Title
**Severity:** Critical/High/Medium/Low
**Environment:** Production/Staging/Dev

### Expected Behavior
What should happen

### Actual Behavior
What actually happens (with error messages)

### Steps to Reproduce
1. Step one
2. Step two
3. Observe issue

### Impact
How this affects users/business
```

**Critical Success Factors:**
- Reproducible steps (100%)
- Environment info (100%)
- Business impact stated (90%)
- Screenshots or logs (80%)
</default_to_action>

## Quick Reference Card

### Severity Levels

| Level | Definition | Examples |
|-------|------------|----------|
| **Critical** | System down, data loss, security | DB deleted, payments broken, credentials exposed |
| **High** | Major feature broken, many users | Can't checkout, search broken, dashboard fails |
| **Medium** | Partial break, workaround exists | Filter broken (refresh works), slow export |
| **Low** | Cosmetic, rare edge case | Button wraps on mobile, tooltip wrong color |

### Title Formula
❌ Bad: "Checkout broken"
✅ Good: "Payment fails with Visa cards when order total > $1000"

**Pattern:** `[Component] fails [Condition] causing [Impact]`

---

## Essential Information

### Environment Details
```
Browser: Chrome 120.0.6099.109 (Windows)
OS: Windows 11 Pro
URL: https://example.com/checkout
Date/Time: 2025-10-17 14:23 UTC
User: test@example.com (ID: 12345)
Request ID: abc-123-def-456
```

### Supporting Evidence

**Error Messages:**
```json
{
  "error": "Payment service unavailable",
  "code": "GATEWAY_TIMEOUT",
  "requestId": "abc-123-def-456"
}
```

The rest: https://github.com/proffesor-for-testing/agentic-qe/blob/HEAD/.claude/skills/bug-reporting-excellence/SKILL.md