triage

Verify and classify issue tracker reports, then recommend category and state labels.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Incoming bug reports and enhancement requests often arrive under-specified, unreproduced, or mislabeled, forcing maintainers to spend time investigating before any work can begin. This Skill investigates a single issue, attempts reproduction, and prepares a classification recommendation so the maintainer only has to confirm a decision. ## Core Features & Use Cases - Issue verification and reproduction: Reads the full issue thread, explores the affected code, and attempts to reproduce reported bugs before recommending a label. - Label state machine: Maps the project's actual label vocabulary onto a model of two category labels (bug, enhancement) and five state labels (needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix). - Agent-ready briefs: Produces structured briefs with problem statement, reproduction steps, acceptance criteria, likely files, and out-of-scope items for downstream agents or humans. - Use Case: A maintainer faces a backlog of untriaged GitHub issues. They invoke the Skill on the queue, review each recommendation, and confirm labels, leaving every issue either ready for work, awaiting reporter info, or durably closed. ## Quick Start Triage issue #42 and recommend how it should be classified.

Frequently Asked Questions about triage

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

FAQPage Schema
How do I triage incoming GitHub issues with an AI agent?▼

Invoke the triage skill with an issue URL or ID like #42, or name a queue to work through. The agent reads the full thread, explores the affected code, attempts reproduction, and recommends category and state labels for your confirmation.

How to prepare an issue for an autonomous coding agent?▼

Triage the issue into the ready-for-agent state, which requires an agent brief containing a problem statement, reproduction steps, acceptance criteria, files likely involved, and explicit out-of-scope items. The skill refuses to apply the label without that brief.

Does issue triage work with Jira, Linear, or GitLab?▼

Yes, the skill is tracker-agnostic and discovers the project's tracker from session context, convention files, or an authenticated CLI rather than assuming a host. It also maps the project's existing label vocabulary onto its default category and state model.

Can the triage agent apply labels or close issues automatically?▼

No, the agent only recommends classifications and waits for maintainer confirmation before applying labels, posting comments, or closing anything. It also never modifies source code, tests, or configuration during triage.

What happens when a bug report cannot be reproduced?▼

The agent reports what it tried and what happened instead, which is a strong signal for the needs-info state. It then posts triage notes with specific questions naming what is missing and why it matters, rather than a generic request for more info.