SkillbookTry free skill
Build & Code / D17
Pro
Preview cut from the real Pro body

Prepare a bug report for an engineer

Turn a messy complaint into repro steps, expected behavior, evidence, environment, and severity.

For
Support, PMs
Time per use
7 min
Format
.md and .skill
How to use it
  1. 1.
    Open ChatGPT or Claude.
    Either works. The skill is just text.
  2. 2.
    Inspect the real preview, then unlock the full file.
    One click; no install, no setup.
  3. 3.
    Paste it as your first message.
    The assistant now knows how to do this one job.
  4. 4.
    Give it your specifics, get the result.
    Roughly 7 min, every time you need it.
Skill filed17-prepare-a-bug-report-for-an-engineer.skill.md1.4 KB
Run once
Advanced
Install permanently ↓

Mobile apps: if ChatGPT or Claude opens blank, tap the message box and paste. Skillbook copies first.

Install

Mobile apps: if ChatGPT or Claude opens blank, tap the message box and paste. Skillbook copies first.

Fill the blanks first.

These fields update the skill preview and the ChatGPT/Claude buttons instantly.

IncludeUser complaint, screenshots described in text, recording notes, logs, browser/device, URL, account state, or thread.
IncludeWhat should have happened?
IncludeWhat happened instead?
IncludeHow many users, severity, money, blocked task, workaround, urgency, or business impact.
IncludeRefresh, different device, repro attempts, support steps, logs checked, or temporary workaround.
Install as agent behavior

Permanent agent install needs the full body.

This page is only showing a preview. Unlock the full skill to install it in Claude Code, Claude Projects, or a Custom GPT.

Unlock full skill →
# Prepare a bug report for an engineer

You are a product support engineer. I will paste a messy bug complaint, support thread, screenshot notes, or screen recording summary. Turn it into a report an engineer can act on.

## Inputs

Bug context: {{bug_context||User complaint, screenshots described in text, recording notes, logs, browser/device, URL, account state, or thread.}}
Expected behavior: {{expected_behavior||What should have happened?}}
Actual behavior: {{actual_behavior||What happened instead?}}
Impact: {{impact||How many users, severity, money, blocked task, workaround, urgency, or business impact.}}
Known attempts: {{known_attempts||Refresh, different device, repro attempts, support steps, logs checked, or temporary workaround.}}

## Output

**1. Bug title.** Clear and searchable.

**2. Summary.** One paragraph with user impact.

**3. Reproduction steps.** Numbered, minimal, and specific.

**4. Expected vs actual.** Side-by-side.

**5. Environment.** Device, browser, account, role, URL, build, time, flags, or data.

**6. Evidence.** Logs, screenshots, videos, user quotes, and what is still missing.

**7. Severity recommendation.** P0/P1/P2/P3 with reasoning.

**8. Engineer questions.** The shortest list of unknowns.

## Rules

[Preview stops here. Unlock the Pro library for the full rules, guardrails, examples, and copyable file.]
The rest is in the Pro library.

This preview is cut from a real Pro workflow. Unlock the founding Pro library for the full file, rules, examples, and installable skill.

Full Pro file includes
  • ✓ Input checklist
  • ✓ Step-by-step workflow
  • ✓ Quality bar
  • ✓ Guardrails
  • ✓ Output format
  • ✓ Example run
  • ✓ Install formats
Unlock the library →
Other things on the Build & Code shelf
ID D01
Turn an app idea into a build plan
ID D02
Debug an error from logs
ID D03
Review a pull request