triage

Assign bug or enhancement and state roles to GitHub issues with next steps.

Updated May 11, 2026
One-click install
npx skills add https://github.com/IsKenKenYa/Commory --skill triage-iskenkenya
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/IsKenKenYa/Commory/tree/main/.windsurf/skills/triage
Command: npx skills add https://github.com/IsKenKenYa/Commory --skill triage-iskenkenya

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Triage guidance is missing or inconsistent when issues move through different stages, causing delays, repeated questions, and slower handoff to agents or humans.

Core Features & Use Cases

  • Issue state machine triage: Applies exactly one category role (bug/enhancement) and one state role (needs-triage/needs-info/ready-for-agent/ready-for-human/wontfix) to keep workflow consistent.
  • Durable agent-ready specification: Generates agent brief comments that capture behavior and acceptance criteria reliably over time.
  • Out-of-scope deduplication: Leverages a persistent out-of-scope knowledge base to reuse previous rejection reasoning for similar enhancement requests.
  • Targeted workflows: Supports both “show what needs attention” summaries and “triage a specific issue” recommendations with optional grilling steps.

Quick Start

Use the triage skill to move issue #42 to ready-for-agent after evaluating its context and generating an agent brief when appropriate.

Frequently Asked Questions about triage

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

FAQPage Schema
How do I triage GitHub issues using a state machine for consistent bug and enhancement labels?

Triage GitHub issues by assigning exactly one category role (bug/enhancement) and one state role to maintain workflow consistency, preventing delays and repeated questions during issue processing.

What is the best way to generate agent briefs from GitHub issues with acceptance criteria?

Generate agent brief comments during issue triage by capturing behavior and acceptance criteria, creating durable specifications that reliably prepare AFK agent work over time.

Can I deduplicate out-of-scope enhancement requests using previous rejection reasoning?

Yes, leverage a persistent out-of-scope knowledge base to reuse previous rejection reasoning for similar enhancement requests, automatically deduplicating rejected enhancements during triage.

Does GitHub issue triage work with role-based labels for needs-info and ready-for-agent states?

Yes, role-based issue labels support states including needs-triage, needs-info, ready-for-agent, ready-for-human, and wontfix, ensuring targeted workflow management across different issue stages.

Why does consistent issue triage matter for handoff to human or agent workflows?

Consistent issue triage prevents missing guidance when issues move through different stages, reducing delays and slower handoff to agents or humans caused by repeated questions.