triage

Enforce role-based state-machine workflows for issue triage across trackers.

195|16|Updated Feb 18, 2025

Search Tags:#automation #workflow #github #agent #issues #triage #state-machine

Ready to run

npx skills add https://github.com/InditexTech/weavejs --skill triage-inditextech

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/InditexTech/weavejs/tree/main/code/.agents/skills/triage
Command: npx skills add https://github.com/InditexTech/weavejs --skill triage-inditextech

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Triage issues efficiently by applying a defined state-machine with roles to categorize and route issues, reducing manual triage workload.

Core Features & Use Cases

Role-based triage: categorize issues with category and state roles (needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix) and ensure consistency.
Invocation and workflow: guide maintainers to move issues through the canonical states and surface agent briefs when ready for automation.
Context-aware guidance: surface relevant documentation like AGENT-BRIEF.md and OUT-OF-SCOPE.md during triage to inform decisions.

Quick Start

Invoke the /triage command to begin categorizing an issue and generate 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?▼

You can automate GitHub issue triage by applying a configurable state machine that enforces canonical roles and transitions, routing items to needs-triage, needs-info, ready-for-agent, ready-for-human, or wontfix states.

What is state-driven triage for issue trackers?▼

State-driven triage enforces a single category and state per issue using role-based classifications, ensuring consistent routing and reducing manual workload across issue trackers.

How do I route GitHub issues to an automated agent?▼

Move issues through the triage state machine to the ready-for-agent state, which surfaces agent briefs and relevant documentation to trigger automation workflows.

Does this issue triage workflow support wontfix and needs-info states?▼

Yes, the triage state machine supports needs-triage, needs-info, ready-for-agent, ready-for-human, and wontfix workflows, ensuring each issue receives exactly one category and state.

What's the best way to ensure consistent issue categorization across a team?▼

Enforce canonical roles and state transitions through a state-driven triage process that surfaces relevant reference documents like AGENT-BRIEF.md and OUT-OF-SCOPE.md during categorization.

How do I start triaging an issue using this workflow?▼

Invoke the /triage command to begin categorizing an issue, guiding maintainers through canonical state transitions and generating an agent brief when the issue is ready.