One-click install
npx skills add https://github.com/haryelramalho/skills --skill triage-haryelramalho
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/haryelramalho/skills/tree/main/skills/community/triage
Command: npx skills add https://github.com/haryelramalho/skills --skill triage-haryelramalho

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps maintainers move GitHub issues from uncertainty to a clear next step by classifying, reproducing, clarifying, or handing them off with durable context.

Core Features & Use Cases

  • Issue routing: Distinguishes bugs from enhancements and places each issue into the right triage state.
  • Context gathering: Reviews issue history, comments, and prior triage notes so work does not repeat or lose progress.
  • Bug handling: Recommends reproduction steps, reports results, and identifies when more information is needed.
  • Agent-ready handoff: Writes structured agent briefs with acceptance criteria and scope boundaries for AFK implementation.
  • Out-of-scope tracking: Records rejected enhancements in a persistent knowledge base so similar requests can be recognized later.

Quick Start

Ask the triage skill to review a specific GitHub issue and recommend the correct next state with a concise explanation.

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 classifies GitHub issues by distinguishing bug reports from feature requests and placing each into the correct triage state. It evaluates issue history and comments to route items accurately for backlog review and enhancement evaluation.

What is the best way to reproduce GitHub bug reports during issue triage?

Bug reproduction during triage involves recommending specific steps, reporting the results, and identifying when more information is needed from the reporter. This ensures bugs are verified before moving to the next workflow state.

How do I create agent briefs for GitHub issues requiring AFK implementation?

Creating agent briefs involves writing structured handoff documents with acceptance criteria and scope boundaries. This provides durable context for AFK implementation, ensuring autonomous agents receive clear instructions from the triage process.

Can I track rejected feature requests in a knowledge base to prevent duplicate issues?

Yes, out-of-scope tracking records rejected enhancements in a persistent knowledge base. This allows maintainers to recognize similar requests later during issue triage and prevents repeated evaluation of the same feature requests.

How do I check label-state consistency when reviewing a GitHub issue backlog?

Label-state consistency checks verify that issue labels accurately reflect the current triage state. The skill reviews issue history and prior triage notes to ensure labels match the determined next steps and prevent workflow misalignment.

What should I do when a GitHub issue lacks enough context for triage decisions?

Context gathering reviews issue history, comments, and prior triage notes to recover missing information. If insufficient details remain, the triage process identifies when more information is needed and requests clarification from the reporter.