القائمة
Review new product, bug, support, and docs issues. Use when classifying GitHub issues, assigning labels, and deciding whether more information is required.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Convert a product requirements document into small, independently executable engineering issues. Use when a PM, designer, or engineer wants implementation work broken into delivery slices.
Draft customer-facing and internal release notes from merged work. Use when summarizing shipped changes for users, support, sales, or internal stakeholders.
| name | issue-triage |
| description | Review new product, bug, support, and docs issues. Use when classifying GitHub issues, assigning labels, and deciding whether more information is required. |
| version | 1.0 |
| license | See repository license |
Help the product team route incoming issues quickly and consistently.
You may inspect:
For each issue:
type:* labelarea:* labelseverity:* labelChoose one:
type:bugtype:featuretype:supporttype:docstype:duplicateChoose one:
area:webarea:adminarea:apiarea:autharea:billingarea:notificationsarea:analyticsarea:docsChoose one:
severity:critical - outage, security risk, data loss, billing breakage, or blocked core workflow for many usersseverity:high - major feature broken and no reliable workaroundseverity:medium - meaningful defect with limited scope or workaround availableseverity:low - minor issue, edge case, cosmetic problem, or low-impact docs gapAn issue is actionable if it contains enough information to begin investigation.
Usually sufficient:
If the issue is not actionable, ask for only the minimum missing detail.
Apply type:duplicate only when a clear canonical issue exists and the symptom strongly matches.
When uncertain, do not mark as duplicate.
When more information is needed: