quality-bug-triage

Convert informal bug reports into structured tickets with severity and reproduction steps.

Updated Jan 6, 2026

Search Tags:#workflow #qa #ticket #triage #severity #bug

Ready to run

npx skills add https://github.com/cslsoftwares/ParamentersORM --skill quality-bug-triage

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: quality-bug-triage
Source: https://github.com/cslsoftwares/ParamentersORM/tree/main/.cursor/skills/quality-bug-triage_V1.0.0
Command: npx skills add https://github.com/cslsoftwares/ParamentersORM --skill quality-bug-triage

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Transform informal bug reports into structured, actionable tickets that capture severity, impact, reproduction steps, and the responsible area, enabling faster triage and assignment without attempting a fix.

Core Features & Use Cases

Structured ticket generation: captures title, severity (S1–S4), impact, reproduction steps, environment, and area.
Rapid triage workflow: prioritizes tickets for the correct team and routes them to the appropriate queue.
Audit-ready outputs: produces consistent tickets suitable for logging, reporting, and SLA tracking.

Quick Start

Provide a bug report with a description, reproduction steps, and environment, and I will generate a structured triage ticket.

Frequently Asked Questions about quality-bug-triage

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

FAQPage Schema

How do I convert informal bug reports into structured triage tickets?▼

To convert informal bug reports into structured triage tickets, provide a description, reproduction steps, and environment. The workflow outputs a ticket with title, severity (S1–S4), impact, steps, environment, and the responsible area.

What is the best way to prioritize bug tickets before assigning them across modules?▼

Prioritize bug tickets by applying a triage workflow that assesses severity and estimated impact. This generates audit-ready tickets with an assigned responsible area, enabling clear prioritization and correct team routing before module assignment.

Can I use a bug triage workflow for reports received via chat, email, and logs?▼

Yes, you can apply this bug triage workflow to reports received via chat, email, logs, or issue trackers. It enforces required inputs like description and reproduction steps to produce consistent, actionable tickets regardless of the source channel.

What required inputs do I need to generate a bug ticket with severity and impact?▼

You need to provide a bug description, reproduction steps, and environment details as required inputs. The triage process uses these to generate a structured ticket containing title, severity (S1–S4), impact, steps, environment, and the responsible area.

Does the triage workflow attempt to fix the bug or just structure the report?▼

The triage workflow only structures the bug report for triage and assignment; it does not attempt a fix. It transforms informal reports into actionable tickets with severity, impact, reproduction steps, and responsible area to enable faster routing.

Why are my bug tickets lacking clear ownership and severity levels?▼

Bug tickets lack clear ownership and severity when informal reports bypass a structured triage workflow. Enforcing required inputs like description and environment ensures outputs include severity (S1–S4), impact, and the responsible area for proper prioritization.