skills.rest
vstorm-co
vstorm-coOFFICIAL
Explore all skills by this author →
WebsiteGitHub

Bug report triage

Triage bug reports into reproducible cases with classified severity and missing information.

49|11|Updated Jul 31, 2026
Search Tags:#qa#issue tracking#regression#bug triage#reproduction steps#severity classification
One-click install
npx skills add https://github.com/vstorm-co/agenticos --skill bug-report-triage-vstorm-co
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Bug report triage
Source: https://github.com/vstorm-co/agenticos/tree/main/backend/app/core/catalog/skill_gallery/software/bug-report-triage
Command: npx skills add https://github.com/vstorm-co/agenticos --skill bug-report-triage-vstorm-co

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Bug reports often arrive vague and unreproducible, leading to tickets that get closed without being fixed. This Skill structures the triage process so every report ends with either a numbered reproduction or a precise list of what is still missing. ## Core Features & Use Cases - Structured Intake: Establishes exact reproduction steps, expected versus actual behavior, environment, version, frequency, and recent changes. - Honest Classification: Distinguishes bugs, regressions, missing features, and works-as-designed cases so tickets are labeled correctly. - Impact-Based Severity: Derives severity from impact and frequency with stated reasoning, not from reporter frustration. - Use Case: A QA engineer receives a report saying "the export button is broken." The Skill guides them to collect steps, browser, and version, classify it as a regression, and produce a numbered reproduction the engineering team can act on immediately. ## Quick Start Triage this bug report and tell me whether it is reproducible or exactly what information is still needed.

Frequently Asked Questions about Bug report triage

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I triage a bug report effectively?▼

Establish exact reproduction steps, expected versus actual behavior, environment, version, frequency, and what changed when the issue started. End every triage with either a numbered reproduction or a specific list of missing information.

How to classify a bug report as bug or feature request?▼

A bug means the software does not do what it says; a regression means it used to work, so find the version where it broke. If it never worked, classify it as a missing feature plainly rather than accepting it as a bug.

How should bug severity be determined?▼

Derive severity from impact and frequency, not from how annoyed the reporter is. State the reasoning explicitly so the assessment can be challenged and debated by the team.

What information is needed to reproduce a bug?▼

You need ordered steps, what happened, what was expected, environment, version and browser, frequency (always, sometimes, once), when it started, and whether other users or tenants are affected.

When should a bug report be closed without a fix?▼

Never close for inactivity without stating what was missing, and never merge two reports just because symptoms look alike. An unreproducible bug without documented gaps is closed, not fixed.

Related Skills

Explore More Software Engineering Skills→
oresttokovenkooresttokovenko

persona-customer-support

Manage customer support tickets, responses, and escalations through Google Workspace CLI workflows.

Community
Intermediate
tomguntomgun

fixing-bugs

Reproduce bugs with regression tests and apply minimal root-cause fixes.

Community
Intermediate
HKU-MMLabHKU-MMLab
39

log-analyzer

Parse, search, and analyze application logs across plain text and JSON formats.

Official
Intermediate
kynoptickynoptic
1

Debugging Runtime Errors

Analyze stack traces and error logs to identify root causes and propose fixes.

Community
Advanced