github-triage

Triage GitHub issues through a label-based state machine with interactive grilling sessions.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/toderian/project_template --skill github-triage-toderian
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-triage
Source: https://github.com/toderian/project_template/tree/main/plugins/agents-extras/skills/github-triage
Command: npx skills add https://github.com/toderian/project_template --skill github-triage-toderian

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Incoming GitHub issues pile up without consistent classification, specification, or routing, forcing maintainers to manually evaluate every bug report and feature request before work can begin. ## Core Features & Use Cases - Label-Based State Machine: Moves issues through defined states (needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix) with enforced transition rules and conflict detection. - Interactive Grilling Sessions: Interviews the maintainer to build complete specifications, resuming from prior triage notes without re-asking resolved questions. - Agent Brief Generation: Writes durable, behavior-focused agent briefs so issues marked ready-for-agent can be picked up by an AFK agent weeks later. - Out-of-Scope Knowledge Base: Records rejected feature requests in .out-of-scope/ files and matches new issues against prior rejections to avoid re-litigating decisions. - Use Case: A maintainer asks "show me anything that needs my attention" and receives a grouped summary of unlabeled, needs-triage, and needs-info issues, then triages issue #42 through reproduction, grilling, and a ready-for-agent brief. ## Quick Start Ask the agent to show all GitHub issues that need attention in the current repository and triage them one by one.

Frequently Asked Questions about github-triage

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

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

Invoke the skill and describe what you want in natural language, such as "show me anything that needs my attention" or "let's look at #42". The skill reads the issue, explores the codebase, presents a category and state recommendation, and applies labels only after your confirmation.

What labels does a GitHub issue triage workflow use?

This workflow uses two category labels (bug, enhancement) and five state labels (needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix). Every issue should have exactly one category and one state label, and conflicting state labels are flagged for maintainer resolution.

How do I prepare a GitHub issue for an autonomous coding agent?

Run a grilling session to flesh out the specification, then move the issue to ready-for-agent. The skill posts an agent brief comment describing current behavior, desired behavior, key interfaces, acceptance criteria, and scope boundaries without referencing file paths or line numbers.

Does the triage skill require the GitHub CLI?

Yes, all GitHub operations go through the gh CLI, and the repository is inferred from the git remote. You need gh installed and authenticated in the environment where the skill runs.

How are rejected feature requests tracked across issues?

Rejected enhancements are recorded in .out-of-scope/<concept>.md files containing the decision, reasoning, and links to prior requests. During triage, new issues are matched against these files by concept similarity so prior rejections are surfaced instead of re-litigated.

Can I override the triage state machine directly?

Yes, a maintainer can explicitly move an issue to any state, such as "move #42 to ready-for-agent". The skill applies the label directly, skipping the grilling session, but still shows a confirmation of which labels and comments will change.