Verified:GitHub

triage

Triage GitHub issues by applying category and state workflow roles.

3|Updated May 11, 2026

Search Tags:#release management #workflow automation #github #issue triage #bug reproduction #label management #AFK agent briefing

Ready to run

npx skills add https://github.com/JeromyJSmith/lattice-platform --skill triage-jeromyjsmith

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/JeromyJSmith/lattice-platform/tree/main/.agents/skills/triage
Command: npx skills add https://github.com/JeromyJSmith/lattice-platform --skill triage-jeromyjsmith

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps maintainers quickly and consistently triage GitHub issues by routing them through an explicit state machine with clear roles for bugs and enhancements.

Core Features & Use Cases

Category + state enforcement: Ensures each issue ends up with exactly one category role (bug or enhancement) and one state role (e.g., needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix).
Durable delegation: Produces an AFK-ready agent brief (or a human-ready brief when delegation isn’t appropriate) so work can proceed without the maintainer being present.
Evidence-based refinement: For bugs, performs reproduction guidance and escalates to needs-info when details are insufficient, reducing back-and-forth.

Quick Start

Ask the AI to triage your incoming issues by running /triage and describing what you want it to move, review, or summarize.

Frequently Asked Questions about triage

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

FAQPage Schema

How do I automate GitHub issue triage with a clear state workflow?▼

Automate GitHub issue triage by applying a category (bug or enhancement) and a state role like needs-triage or ready-for-agent based on maintainer intent and issue context. The workflow enforces explicit state transitions to route issues efficiently.

What is the best way to handle bug reproduction and request missing info on GitHub issues?▼

Bug reproduction handling involves evaluating issue details and escalating to a needs-info state when details are insufficient. This reduces back-and-forth by requesting missing information explicitly before proceeding.

How do I prepare AFK agent briefs from GitHub issues?▼

Prepare AFK agent briefs by generating durable delegation outputs from triaged GitHub issues. When delegation is appropriate, the brief allows work to proceed without the maintainer being present.

Can I enforce label management for bugs and enhancements on GitHub?▼

Label management enforces exactly one category role (bug or enhancement) and one state role per issue. States include needs-triage, needs-info, ready-for-agent, ready-for-human, and wontfix.

Does GitHub issue triage require emitting specific comments with disclaimers?▼

Issue triage requires emitting triage comments that include a required AI disclaimer. It also involves reading reference guidance and driving state transitions with explicit acceptance criteria.

When should I move a GitHub issue to wontfix instead of ready-for-human?▼

Move an issue to wontfix based on maintainer intent and out-of-scope decisions during triage. If the issue is in scope but requires manual handling, it transitions to ready-for-human instead.