triage

Convert GitHub and Jira issues into structured state-driven triage plans.

3|1|Updated Mar 23, 2026

Search Tags:#workflow #github #jira #triage #state-machine #agent-brief

Ready to run

npx skills add https://github.com/malinskibeniamin/skills --skill triage-malinskibeniamin

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/malinskibeniamin/skills/tree/main/triage
Command: npx skills add https://github.com/malinskibeniamin/skills --skill triage-malinskibeniamin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Triage issues across GitHub and Jira without losing context, providing a structured state-machine workflow that moves issues through defined roles and ensures consistent communication.

Core Features & Use Cases

Structured triage with explicit roles (needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix) and state transitions
Cross-tracker support for GitHub and Jira, plus artifacts like agent briefs and out-of-scope notes
Generates actionable steps and ensures discourse is captured for AFK agent handoff

Quick Start

Invoke the /triage command on a new or existing issue to begin structured triage and generate an agent brief.

Frequently Asked Questions about triage

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

FAQPage Schema

How do I triage GitHub and Jira issues without losing context across trackers?▼

Triage issues across GitHub and Jira without losing context by using a structured state-machine workflow that moves issues through defined roles and ensures consistent communication. It consolidates scattered issue information into actionable steps.

What is the best way to move Jira issues through needs-triage and ready-for-agent states?▼

Moving Jira issues through needs-triage and ready-for-agent states is handled by a structured triage workflow with explicit roles and state transitions. It applies tracker-specific commands to publish or fetch tickets during the process.

How do I generate an agent brief for GitHub issues before automated handoff?▼

Generating an agent brief for GitHub issues is done by reading the issue context and out-of-scope notes, then producing a structured plan. This ensures discourse is captured for AFK agent handoff.

Can I use gh and acli commands to fetch and publish tickets during issue triage?▼

Yes, you can use gh and acli commands to fetch and publish tickets. The triage workflow relies on these tracker-specific commands to manage GitHub and Jira issues as part of its state transitions.

How do I manage out-of-scope notes when triaging issues across multiple trackers?▼

Managing out-of-scope notes during triage involves reading existing .out-of-scope files to filter irrelevant issues. The workflow generates wontfix states and out-of-scope notes to maintain a clean backlog across GitHub and Jira.

Does cross-tracker issue triage support both human and automated agent handoff?▼

Cross-tracker issue triage supports both human and automated agent handoff by moving issues into ready-for-agent and ready-for-human states. It generates agent briefs to ensure seamless context transfer.