Skip to content

skillWorkflow

Bug Report Triage

Triages an incoming bug report, tries to reproduce it, and writes a minimal repro with a severity and the next step for the owner.

npx workspacetemplates add bug-report-triage --tool claude-code

Writes 1 file to .claude/skills/bug-report-triage/

.claude/skills/bug-report-triage/SKILL.md27 lines · 1.9 KBFile
---
name: bug-report-triage
description: Triages an incoming bug report, tries to reproduce it, and writes a minimal repro with a severity and the next step for the owner.
---

# Bug report triage

Verdict and repro first. Do not fix the bug in this skill.

## Steps

1. Extract the claims: expected behavior, actual behavior, environment (version, platform, browser, account type), and the steps if any. List what is missing.
2. Check for duplicates and known fixes: search issues and the changelog for the error text and the feature name, and look at recent commits touching the area. If it is fixed in a newer version, say which.
3. Try to reproduce on the current main branch. Start from the reporter's steps. Capture exact commands, inputs and output. Try once more with a clean state to rule out leftover data.
4. If it reproduces, shrink it. Remove steps and data until each remaining one is needed. Aim for a failing test, a script of under ten lines, or at most five manual steps.
5. If it does not reproduce, say what you tried and in which environment, then list the specific facts that would help: version, logs, request ID, account type, time. Do not close the report yourself.
6. Locate, lightly. Name the module and the likely cause only if the evidence supports it. Mark the confidence as high, medium or low.
7. Rate severity. Critical: data loss, security or payment impact, or a total outage. High: a main flow is broken with no workaround. Medium: broken with a workaround. Low: cosmetic or rare. State the number of affected users when the logs show it.

## Rules

- Never edit source code. A repro test goes in a new file or the comment, not in the suite.
- Never include customer personal data in the report. Replace it with placeholders.

## Report

Verdict (reproduced, not reproduced, duplicate, needs info), severity, minimal repro, suspected area with confidence, and the suggested owner or label.

What it does

Bug reports arrive as screenshots, half sentences and 'it just broke'. This skill has the agent turn each one into a verdict: reproduced or not, how bad, and where the problem probably sits, backed by a repro someone else can run in a minute.

It does not fix the bug. The goal is a report an engineer can pick up without a single follow-up question, or a clear reason why the report cannot move yet.

Example

you › Triage this: 'Invoices show the wrong total sometimes. Please fix ASAP.'

agent › Verdict: reproduced. Severity: high, since totals are wrong on paid invoices. Repro: create an invoice with two lines at 19.99 and quantity 3, apply a 10% discount; the total shows 53.97 and should show 53.97 minus 5.40. Fails when the discount applies after rounding per line. Suspected: src/billing/totals.ts rounds each line before the discount. Confidence medium. Not a duplicate. Label: billing.

Questions

Will it close reports it cannot reproduce?
No. It lists exactly what was tried and what information is missing, so the reporter or an engineer decides whether to close.
What counts as a minimal repro?
The shortest sequence that still fails: a test, a short script or a few steps where removing any step makes the problem disappear.
  • Codebase Onboarding

    SkillWorkflow

    Free
  • Context Management

    SkillWorkflow

    Free
  • Library Selection

    SkillWorkflow

    Free