triage

Classify GitHub issues into categories and states with triage notes.

Updated May 31, 2026
One-click install
npx skills add https://github.com/anonymousminati/Res-POS --skill triage-anonymousminati
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/anonymousminati/Res-POS/tree/main/.claude/skills/triage
Command: npx skills add https://github.com/anonymousminati/Res-POS --skill triage-anonymousminati

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps maintainers turn a backlog of GitHub issues into a clear, actionable workflow by classifying, prioritizing, and routing each issue to the right state.

Core Features & Use Cases

  • Issue classification: Assign exactly one category and one state so bugs, enhancements, and follow-up work stay organized.
  • Context gathering and review: Read issue details, prior comments, and existing triage notes to avoid repeating questions or missing resolved answers.
  • Bug reproduction and escalation: Confirm problems when possible, gather missing details when needed, and decide whether an issue should go to an agent, a human, or be marked wontfix.
  • Out-of-scope tracking: Record rejected enhancement concepts in a durable knowledge base so similar future requests can be handled consistently.
  • Use case: A maintainer asks for help with a new issue, and this Skill recommends the next state, drafts the required comment, and preserves the workflow contract for later action.

Quick Start

Ask the triage skill to review a specific issue or show what needs attention, then follow its recommendation for the next state and comment.

Frequently Asked Questions about triage

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

FAQPage Schema
How do I automate GitHub issue triage to classify bugs and feature requests?

Automating GitHub issue triage involves classifying each report by assigning exactly one category and one state. This skill reviews issue context and prior comments to recommend the correct routing, ensuring bugs and enhancements stay organized without repeating questions.

What is the best way to handle out-of-scope enhancement requests on GitHub?

Handling out-of-scope enhancement requests requires recording rejected concepts in a durable knowledge base. This skill tracks wontfix decisions durably so similar future feature requests can be handled consistently and immediately.

How do I prepare GitHub issues for an AI agent to resolve?

Preparing GitHub issues for an AI agent requires gathering missing details and confirming the bug. This skill reproduces problems when needed, gathers necessary context, and generates durable agent briefs to transition issues to ready-for-agent.

Can I use this to draft needs-info follow-up comments for missing bug details?

Yes, you can draft needs-info follow-up comments for missing bug details. The skill evaluates issue context, identifies missing information, and drafts the required comment to request the necessary reproduction steps.

Does GitHub issue triage require reproducing the reported bug?

Reproducing the bug is required when possible during GitHub issue triage. The skill confirms problems to decide whether an issue should escalate to a human, go to an agent, or be marked wontfix based on verified behavior.