triage

Assign category and state to GitHub issues using a state-machine workflow.

Updated Apr 29, 2026
One-click install
npx skills add https://github.com/remiconnesson/nuxt-minimal-starter-v0-template --skill triage-remiconnesson
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/remiconnesson/nuxt-minimal-starter-v0-template/tree/main/.agents/skills/triage
Command: npx skills add https://github.com/remiconnesson/nuxt-minimal-starter-v0-template --skill triage-remiconnesson

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Triage issues on a project tracker by applying a structured state-machine workflow that enforces consistent category and status decisions, helping maintainers and AFK agents move work forward without ambiguity.

Core Features & Use Cases

  • Enforces one category and one state per issue to standardize triage decisions.
  • Provides a knowledge-grounded workflow that surfaces prior context from issue history and references.
  • Supports preparing issues for AFK agents or human implementation, and ensures transparent handoffs.

Quick Start

Follow the defined state machine to triage an issue by assigning its category and initial state.

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 using a state machine workflow?

Triage GitHub issues by applying a state-machine workflow that enforces a single category and a single state per issue, routing them to needs-triage, needs-info, ready-for-agent, ready-for-human, or wontfix.

What is the best way to standardize issue tracking categories and states?

Standardize issue tracking by enforcing a principled state machine that assigns exactly one category and one state to each issue, surfacing prior triage context and out-of-scope notes for transparent decisions.

Can I route GitHub pull requests for AFK agents during issue triage?

Yes, issue triage supports GitHub issues and pull requests, routing them to ready-for-agent to prepare work for AFK agents or ready-for-human for human follow-up.

Does the triage workflow support referencing prior context from issue history?

Yes, the triage workflow surfaces prior triage context and out-of-scope notes from issue history when present, and references agent brief guidance during the process.

What are the limitations of using a state machine for issue triage?

The state machine enforces a single category and a single state per issue, which limits routing to predefined states like needs-info or wontfix and restricts overlapping classifications.

How do I prepare GitHub issues for human follow-up during triage?

Prepare issues for human follow-up by routing them to ready-for-human during the state-machine triage workflow, which standardizes category and state while surfacing prior context.