triage

Classify GitHub issues into categories and assign workflow states.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/meisijiya/ohMeisijiyaCode --skill triage-meisijiya
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/meisijiya/ohMeisijiyaCode/tree/main/skills/triage
Command: npx skills add https://github.com/meisijiya/ohMeisijiyaCode --skill triage-meisijiya

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps manage GitHub issue intake by turning ambiguous reports and feature requests into clear next actions, so maintainers can decide what needs triage, more information, agent handoff, or rejection.

Core Features & Use Cases

  • Classifies issues into bug or enhancement and assigns the right workflow state.
  • Reviews issue context, prior triage notes, and prior out-of-scope decisions before recommending a path forward.
  • Produces durable agent briefs for ready-for-agent work and structured triage notes for needs-info cases.
  • Use it when you need to summarize incoming issues, reproduce bugs, prepare an AFK handoff, or communicate a won’t-fix decision consistently.

Quick Start

Use the triage skill to review the selected issue, recommend the correct category and state, and draft the next comment or action for the maintainer.

Frequently Asked Questions about triage

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

FAQPage Schema
How do I triage GitHub issues to determine if they are bugs or feature requests?

Triage GitHub issues by classifying them as bugs or enhancements and assigning the correct workflow state. The skill reviews issue context, prior notes, and out-of-scope decisions before recommending a clear next action.

What is the best way to automate GitHub issue intake and prepare agent handoffs?

Automate GitHub issue intake by producing durable agent briefs for ready-for-agent work. This ensures AFK agent handoffs have structured context, accurate state roles, and mandatory triage disclaimers for maintainers.

How do I handle out-of-scope GitHub issues and communicate a won't-fix decision?

Handle out-of-scope GitHub issues by enforcing a role-based state machine that reviews prior rejection decisions. It drafts structured next-step responses to consistently communicate the won't-fix decision to the reporter.

Can I use a state machine to manage GitHub issue workflows and reporter follow-ups?

Yes, you can use a role-based state machine to manage GitHub issue workflows. It enforces state roles, handles reporter follow-up requests, and generates structured triage notes for issues that need more information.

How do I draft next-step comments for GitHub issues that need more information?

Draft next-step comments for GitHub issues by reviewing the issue context and prior triage notes. The skill generates structured triage notes and mandatory disclaimers to clearly request missing information from the reporter.

What are the limitations of using automated triage for GitHub issue categorization?

Automated GitHub issue triage relies on existing issue context and prior notes to assign categories. It cannot independently reproduce bugs or verify technical constraints outside the provided issue metadata and state machine rules.