How do I install the Issue Triage skill?

Run npx skillmds add wildwasser/issue-triage in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Issue Triage skill do?

Triage and manage GitHub issues. Use when reviewing issues or planning work. It is listed under Coding & Dev Tools on SkillMD.

Is Issue Triage safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Issue Triage?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Issue Triage free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Issue Triage?

wildwasser (@wildwasser) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Issue Triage by wildwasser — Agent Skill

Name: Issue Triage
Rating: 4.2 (5 reviews)
Author: wildwasser

File contents

Triage Process

1. Review Issue

# List open issues
gh issue list

# View specific issue
gh issue view <number>

# List with labels
gh issue list --label "bug"

2. Validate Issue

For Bugs

Can the issue be reproduced?
Is there enough information?
Is it a duplicate?
Is it actually a bug (not user error)?

For Features

Is the request clear?
Does it align with project goals?
Is it a duplicate?
Is scope reasonable?

3. Apply Labels

# Add labels
gh issue edit <number> --add-label "bug,priority:high"

# Remove labels
gh issue edit <number> --remove-label "needs-triage"

Standard Labels

Label	Description
`bug`	Something isn't working
`enhancement`	New feature request
`documentation`	Docs improvement
`good-first-issue`	Good for newcomers
`help-wanted`	Extra attention needed
`duplicate`	Already exists
`wontfix`	Won't be addressed
`invalid`	Not valid issue

Priority Labels

priority:critical - Production down, security issue
priority:high - Major functionality broken
priority:medium - Important but not urgent
priority:low - Nice to have

Size Labels

size:S - Small, < 1 day
size:M - Medium, 1-3 days
size:L - Large, 3-5 days
size:XL - Extra large, needs breakdown

4. Respond & Assign

# Add comment
gh issue comment <number> --body "Thanks for reporting! I can reproduce this."

# Assign
gh issue edit <number> --add-assignee @username

# Close as duplicate
gh issue close <number> --comment "Duplicate of #123" --reason "not planned"

# Close as completed
gh issue close <number> --comment "Fixed in #456"

5. Link to Project

# Add to project board
gh issue edit <number> --add-project "Project Name"

Triage Response Templates

Needs More Info

Thanks for reporting! To help us investigate, could you provide:
- Steps to reproduce
- Expected vs actual behavior
- Environment (OS, version, etc.)

Duplicate

Thanks for reporting! This appears to be a duplicate of #XXX. 
I'm closing this issue, but please follow the linked issue for updates.

Won't Fix

Thanks for the suggestion! After consideration, we've decided not to 
implement this because [reason]. Feel free to discuss further if you disagree.

---name: issue-triagedescription: Triage and manage GitHub issues. Use when reviewing issues or planning work.---## Triage Process### 1. Review Issue```bash# List open issuesgh issue list# View specific issuegh issue view <number># List with labelsgh issue list --label "bug"```### 2. Validate Issue#### For Bugs- [ ] Can the issue be reproduced?- [ ] Is there enough information?- [ ] Is it a duplicate?- [ ] Is it actually a bug (not user error)?#### For Features- [ ] Is the request clear?- [ ] Does it align with project goals?- [ ] Is it a duplicate?- [ ] Is scope reasonable?### 3. Apply Labels```bash# Add labelsgh issue edit <number> --add-label "bug,priority:high"# Remove labelsgh issue edit <number> --remove-label "needs-triage"```#### Standard Labels| Label | Description ||-------|-------------|| `bug` | Something isn't working || `enhancement` | New feature request || `documentation` | Docs improvement || `good-first-issue` | Good for newcomers || `help-wanted` | Extra attention needed || `duplicate` | Already exists || `wontfix` | Won't be addressed || `invalid` | Not valid issue |#### Priority Labels- `priority:critical` - Production down, security issue- `priority:high` - Major functionality broken- `priority:medium` - Important but not urgent- `priority:low` - Nice to have#### Size Labels- `size:S` - Small, < 1 day- `size:M` - Medium, 1-3 days- `size:L` - Large, 3-5 days- `size:XL` - Extra large, needs breakdown### 4. Respond & Assign```bash# Add commentgh issue comment <number> --body "Thanks for reporting! I can reproduce this."# Assigngh issue edit <number> --add-assignee @username# Close as duplicategh issue close <number> --comment "Duplicate of #123" --reason "not planned"# Close as completedgh issue close <number> --comment "Fixed in #456"```### 5. Link to Project```bash# Add to project boardgh issue edit <number> --add-project "Project Name"```## Triage Response Templates### Needs More Info```Thanks for reporting! To help us investigate, could you provide:- Steps to reproduce- Expected vs actual behavior- Environment (OS, version, etc.)```### Duplicate```Thanks for reporting! This appears to be a duplicate of #XXX. I'm closing this issue, but please follow the linked issue for updates.```### Won't Fix```Thanks for the suggestion! After consideration, we've decided not to implement this because [reason]. Feel free to discuss further if you disagree.```

Frequently asked questions