triage

Manage GitHub issue lifecycles with a structured state machine via the gh CLI.

1|2|Updated May 27, 2026
One-click install
npx skills add https://github.com/dividedby/skills --skill triage-dividedby
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/dividedby/skills/tree/main/skills/config/triage
Command: npx skills add https://github.com/dividedby/skills --skill triage-dividedby

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill removes the manual overhead of managing GitHub issue trackers by enforcing a consistent state machine for labels, categories, and sizing.

Core Features & Use Cases

  • State Machine Enforcement: Ensures every issue is correctly labeled with state, category, and size, preventing backlog drift.
  • Intelligent Routing: Automatically handles skill requests and bug reports by delegating to specialized workflows or capturing reproduction steps.
  • Use Case: A maintainer can use this to quickly identify unlabelled issues, move items to an agent-ready state, or reject out-of-scope requests with a durable rationale.

Quick Start

Ask the agent to show you what needs attention on the current repository issue tracker.

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 and prevent backlog drift?

Automating GitHub issue triage uses a structured state machine to enforce consistent labels for state, category, and sizing. This prevents backlog drift by ensuring every issue is correctly categorized throughout its lifecycle.

Do I need the GitHub CLI to manage issue workflow states?

Yes, managing issue workflow states with this skill requires the GitHub CLI. It relies on the gh CLI to interact with your repository and apply defined label vocabularies for state, category, and size.

How does automated triage handle bug reports and skill requests?

Automated triage handles bug reports and skill requests through intelligent routing, delegating requests to specialized workflows or capturing reproduction steps to maintain accurate issue tracking.

What's the best way to identify unlabelled GitHub issues for backlog grooming?

The best way to identify unlabelled issues for backlog grooming is to use an automated state machine. It flags items needing attention, moves them to an agent-ready state, or rejects out-of-scope requests with a durable rationale.

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

A limitation of using a label state machine for issue tracking is the strict adherence required to defined label vocabularies for state, category, and size. Without these predefined labels, the automated triage workflow cannot correctly route issues.