Issue Triage Skill (For Maintainers)

Triage incoming issues with classification, labeling, and response drafts.

When to Use

• •Maintainer asks to triage issues
• •Maintainer mentions "classify" or "label" issues
• •Maintainer wants to process new/untriaged issues
• •Maintainer asks for help responding to issues

Process

1. •

   Fetch issue details via GitHub MCP

   • •Get issue content, comments, author info
   • •Check issue age and activity
2. •

   Classify the issue

   • •Type: Bug / Feature / Question / Invalid / Duplicate
   • •Priority: Critical / High / Medium / Low
   • •Difficulty: Easy / Medium / Hard
3. •

   Check for duplicates

   • •Search related issues
   • •Calculate similarity
   • •Link related issues
4. •

   Generate recommendations

   • •Suggest labels
   • •Recommend assignee (if possible)
   • •Draft response template

Output Format

Respond in user's language:

# Issue Triage: #[number]

## Quick Assessment
| Aspect | Value |
|--------|-------|
| Type | Bug / Feature / Question / Invalid |
| Priority | Critical / High / Medium / Low |
| Difficulty | Easy / Medium / Hard |
| Valid | Yes / Needs Info / No |

## Summary
[2-3 sentence summary]

## Duplicate Check
- Related: #[number], #[number]
- Duplicate of: [None / #number]

## Recommended Labels
- `bug` / `enhancement` - [reason]
- `good-first-issue` - [if applicable]
- `[component]` - [if applicable]

## Suggested Assignee
@[username] - [reason: recent work on area / domain expert]

## Response Template

### If Valid:

Thanks for reporting this!

[Acknowledgment]

I've labeled this as [labels]. [Context about timeline]

### If Needs More Info:

Thanks for opening this!

Could you please provide:

• • [Missing info 1]
• • [Missing info 2]

### If Duplicate:

This appears to be a duplicate of #[number].

Closing in favor of the existing issue. Please follow there for updates.

Arguments

$ARGUMENTS can include:

• •Issue number: #123
• •Batch mode: --batch
• •Label filter: --label=needs-triage