Skill

Skill: bug-triage

Systematically classify, prioritize, and assign bugs using a structured triage framework. Ensures the right bugs are fixed before launch and nothing critical slips through.

Install

npx claudepluginhub devmuslim/pdm-skills --plugin pdm-quality-testing

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Systematically classify, prioritize, and assign bugs using a structured triage framework. Ensures the right bugs are fixed before launch and nothing critical slips through.

SKILL.md

Similar Skills

agent-eval

Compares coding agents like Claude Code and Aider on custom YAML-defined codebase tasks using git worktrees, measuring pass rate, cost, time, and consistency.

everything-claude-code

157.7k

agent-harness-construction

Designs and optimizes AI agent action spaces, tool definitions, observation formats, error recovery, and context for higher task completion rates.

everything-claude-code

157.7k

accessibility

Designs, implements, and audits WCAG 2.2 AA accessible UIs for Web (ARIA/HTML5), iOS (SwiftUI traits), and Android (Compose semantics). Audits code for compliance gaps.

everything-claude-code

157.7k

Stats

Parent Repo Stars0

Parent Repo Forks0

Last CommitMar 9, 2026

Actions

View Source View Plugin View on GitHub View README

Skill: bug-triage

Purpose

Systematically classify, prioritize, and assign bugs using a structured triage framework. Ensures the right bugs are fixed before launch and nothing critical slips through.

When to Use

Before a release — clearing the bug backlog
After a test cycle — processing QA findings
During production — triaging live incidents

Framework: Bug Triage

Priority Classification (P0–P4)

Priority	Definition	SLA to Fix	Examples
P0 — Critical	System down, data loss, security breach	Immediate (hours)	Login broken, payments failing, data corruption
P1 — High	Major feature broken, no workaround	1–2 days	Key user flow fails, major performance degradation
P2 — Medium	Feature degraded, workaround exists	Current sprint	Form validation issue, minor UI breakage
P3 — Low	Minor issue, cosmetic, edge case	Next sprint	Typo, minor layout issue, rare edge case
P4 — Deferred	Nice to fix, no user impact	Backlog	Code quality, minor inconsistency

Step 1 — Gather Bug List

Ask user to provide:

Bug title / description
Steps to reproduce (if available)
Environment (dev, staging, prod)
Reported by (user, QA, monitoring)

Step 2 — Triage Each Bug

For each bug, assess:

Severity: What breaks? Data? Flow? UI only?
Frequency: How often does it happen? (always / sometimes / rarely)
Affected Users: All users? Specific segment? Internal only?
Workaround: Does one exist?
Release Blocker?: Would you ship with this bug?

Step 3 — Triage Output Table

#	Bug Title	Priority	Severity	Frequency	Release Blocker?	Assignee	Notes
1	...	P1	High	Always	Yes	Dev Team	Blocks checkout
2	...	P3	Low	Rarely	No	—	Defer to next sprint

Step 4 — Release Decision Summary

P0 bugs: X → Must fix before any release
P1 bugs: X → Must fix before planned release date
P2 bugs: X → Fix in sprint or accept with monitoring
P3/P4 bugs: X → Defer

Release Recommendation:

✅ Ready to release (0 P0s, 0 P1s)
⚠️ Release at risk (P1s remain)
❌ Do not release (P0s remain)

Output Format

Triage table sorted by priority
Release decision summary
List of release blockers with owners
Suggested next command: /test-plan or /assess-readiness