triage

Manage GitHub issue lifecycles with state-based triage roles and agent briefs.

28|3|Updated Apr 28, 2026

Search Tags:#project management #workflow automation #github #issue tracking #triage #agent brief

Ready to run

npx skills add https://github.com/Minara-AI/cc-connect --skill triage-minara-ai

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/Minara-AI/cc-connect/tree/main/.claude/skills/triage
Command: npx skills add https://github.com/Minara-AI/cc-connect --skill triage-minara-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill solves the bottleneck of manual issue management by providing a structured state machine to categorize, prioritize, and prepare issues for automated agents.

Core Features & Use Cases

State Machine Workflow: Enforces consistent lifecycle management for bugs and enhancements using defined roles like needs-triage, ready-for-agent, and wontfix.
Agent Brief Generation: Standardizes the creation of authoritative specifications for AFK agents, ensuring high-quality, durable implementation instructions.
Institutional Memory: Integrates with an out-of-scope knowledge base to prevent re-litigating previously rejected feature requests.

Quick Start

Invoke the triage skill to show me all issues that currently require my attention.

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 categorize bugs versus enhancements?▼

Automating GitHub issue triage requires a state machine workflow that categorizes bugs and enhancements using defined roles like needs-triage, ready-for-agent, and wontfix. This ensures consistent lifecycle management and prepares issues for automated agents.

How does institutional memory prevent re-litigating rejected feature requests in issue tracking?▼

Institutional memory prevents re-litigating rejected features by integrating with an out-of-scope knowledge base. When managing issue tracking, this knowledge base flags previously rejected feature requests so they are not revisited, maintaining consistent workflow transitions.

What is the best way to generate structured agent briefs for automated workflow tasks?▼

Generating structured agent briefs is best handled by standardizing authoritative specifications for AFK agents. This creates high-quality, durable implementation instructions that prepare categorized issues for automated workflow execution.

Can I use state-based triage roles with my existing GitHub issue trackers?▼

State-based triage roles operate within GitHub issue trackers by applying lifecycle management states. Integration with issue tracking APIs and local knowledge base files is required to facilitate consistent workflow transitions and categorize issues.

Do I need local knowledge base files to manage the lifecycle of software issues?▼

Local knowledge base files are required to manage the lifecycle of software issues. These files provide the institutional memory needed to prevent re-litigating rejected features and support the issue tracking API integration for workflow automation.

Why does manual issue management create a bottleneck for workflow automation?▼

Manual issue management creates a bottleneck because it lacks a structured state machine to categorize, prioritize, and prepare issues. Applying state-based triage roles solves this by providing consistent workflow transitions for automated agents.