triage

Apply category and state roles to triage GitHub issues through a standardized workflow.

Updated Nov 16, 2022
One-click install
npx skills add https://github.com/kos3nz/dotfiles --skill triage-kos3nz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/kos3nz/dotfiles/tree/main/.config/agents/skills/triage
Command: npx skills add https://github.com/kos3nz/dotfiles --skill triage-kos3nz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Triages GitHub issues by enforcing a standardized state machine with one category and one state, surfacing agent briefs, and guiding maintainers through consistent decision-making.

Core Features & Use Cases

  • Applies canonical roles: category (bug/enhancement) and state (needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix) to issues to enable predictable workflows.
  • Surfaces agent briefs and triage notes when issues are ready for an agent or human review, using templates like AGENT-BRIEF.md and referencing OUT-OF-SCOPE.md for rejected requests.
  • Enforces strict state transitions and prompts with contextual information to minimize duplication and misclassification.
  • Supports invoking triage via /triage and generating actionable next steps for maintainers.

Quick Start

Invoke the /triage command on an unlabeled issue to classify it and attach an agent brief when ready.

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 state machine?

Automating GitHub issue triage involves applying fixed category and state roles to move issues through a standardized workflow. This skill analyzes issue bodies and comments to enforce one-category and one-state constraints, transitioning issues to needs-info, ready-for-agent, or wontfix states.

What is an agent brief in GitHub issue triage?

An agent brief in GitHub issue triage is a contextual summary posted on an issue when it is ready for an agent. It surfaces relevant guidance from templates like AGENT-BRIEF.md to provide actionable next steps for maintainers and automated agents.

How do I classify unlabeled GitHub issues using AI?

Classifying unlabeled GitHub issues using AI requires applying canonical roles like bug or enhancement categories. This skill analyzes issue bodies, comments, and prior triage notes to automatically attach appropriate labels and transition issues to ready-for-human or ready-for-agent states.

Can I enforce strict state transitions for GitHub issues?

Enforcing strict state transitions for GitHub issues is supported by applying a standardized state machine. The triage process prompts with contextual information to minimize misclassification and ensures issues follow valid paths between needs-triage, needs-info, ready-for-agent, ready-for-human, and wontfix states.

How do I reject out-of-scope GitHub issue requests?

Rejecting out-of-scope GitHub issue requests involves referencing an OUT-OF-SCOPE.md file for guidance. The triage workflow analyzes the issue against this criteria and transitions the issue to the wontfix state while posting relevant triage notes for the maintainer.