skills.rest
kartikkabadi
kartikkabadiCOMMUNITY
Explore all skills by this author →
𝕏@1kartikkabadi1GitHub

triage

Classify repository issues into categories and workflow states.

Updated Jul 17, 2026
Search Tags:#workflow#github#handoff#issues#enhancement#triage#bug tracking
One-click install
npx skills add https://github.com/kartikkabadi/skills --skill triage-kartikkabadi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/kartikkabadi/skills/tree/main/triage
Command: npx skills add https://github.com/kartikkabadi/skills --skill triage-kartikkabadi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you manage incoming issues in a disciplined way so you can quickly classify bugs and enhancements, identify what needs more information, and route work to the right next step.

Core Features & Use Cases

  • Issue Classification: Assign each issue exactly one category and one state role so triage stays consistent.
  • Workflow Guidance: Move issues through needs-triage, needs-info, ready-for-agent, ready-for-human, or wontfix with clear rules.
  • Maintainer Support: Summarize what needs attention, read prior triage notes, and prepare strong handoffs for agents or humans.
  • Use Case: A maintainer asks what needs attention today, and this Skill organizes unlabeled issues, waiting-on-reporter issues, and triaged items into actionable buckets.

Quick Start

Use the triage skill to review issue #42 and recommend the correct category and next state based on the reporter’s details and the existing codebase.

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 faster and classify bugs vs enhancements?▼

To triage GitHub issues, assign each issue exactly one category and one state role, ensuring consistent bug and enhancement classification. Review issue history, reproduction evidence, and prior triage notes to route work into actionable workflow states.

What is the best way to organize a GitHub issue queue for agent or human handoff?▼

Organizing an issue queue requires moving items through states like needs-triage, needs-info, ready-for-agent, ready-for-human, or wontfix. This state flow prepares structured handoffs by summarizing what needs attention and routing issues to the correct next step.

How do I manage waiting-on-reporter issues that need more information?▼

Manage waiting-on-reporter issues by applying the needs-info state role during issue triage. This classification isolates unlabeled issues lacking reproduction evidence, allowing maintainers to focus on actionable items while tracking follow-up requirements.

Can I use automated state transitions for bug tracking on repository issue queues?▼

Bug tracking state transitions apply to repository issue queues by following clear workflow rules. You move issues into needs-triage, ready-for-agent, or wontfix states based on reporter details, prior triage notes, and codebase evidence.

When should I mark an issue wontfix during the GitHub triage workflow?▼

Mark an issue wontfix during GitHub triage when disciplined review of issue history and reproduction evidence concludes the bug or enhancement is invalid or out of scope. This state role prevents unnecessary agent or human implementation work.

Related Skills

Explore More Software Engineering Skills→
sQVesQVe

debug-issue

Diagnose bugs by tracing evidence and generating a BR issue template.

Community
Advanced
InditexTechInditexTech
195

triage

Enforce role-based state-machine workflows for issue triage across trackers.

Official
Advanced
Kushal9889Kushal9889

triage

Automate issue triage and state transitions in project management systems.

Community
Intermediate
amazingloft999-droidamazingloft999-droid
356

triage

Classify and route GitHub issues through a state-machine triage workflow.

Community
Advanced