triage

Generate structured agent briefs from GitHub and GitLab issue discussions.

7|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/Davie521/claude-skills --skill triage-davie521
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/Davie521/claude-skills/tree/main/plugins/dev-workflow/skills/triage
Command: npx skills add https://github.com/Davie521/claude-skills --skill triage-davie521

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill standardizes and accelerates how issues are triaged by transforming discussions into durable, actionable agent briefs, reducing ambiguity and enabling consistent follow-through.

Core Features & Use Cases

  • Detects and manages canonical triage states (needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix) and ensures consistent labeling across trackers.
  • Integrates with major trackers (GitHub, GitLab) and provides a local fallback mode, surfacing relevant context from the knowledge base when available.
  • Generates a durable AGENT-BRIEF.md when an issue is ready for an AFK agent, while referencing CONTEXT/ADR guidance and OUT-OF-SCOPE notes as appropriate.

Quick Start

Invoke /triage on an issue to start the triage workflow 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 issue triage for GitHub and GitLab trackers?

Automating issue triage standardizes tracker discussions into structured agent briefs, managing canonical states like needs-triage and ready-for-agent across GitHub and GitLab to enable consistent follow-through.

What is an agent brief and when is it generated during issue triage?

An agent brief is a durable AGENT-BRIEF.md document generated during issue triage when a tracker state reaches ready-for-agent, transforming discussions into actionable context for AFK agents.

How do I standardize triage states across multiple issue trackers?

Standardizing triage states involves enforcing a canonical category and state taxonomy across GitHub and GitLab, ensuring consistent labels like needs-info, ready-for-human, and wontfix are applied.

Does issue triage work without connecting a GitHub or GitLab tracker?

Issue triage provides a local fallback mode when GitHub or GitLab trackers are unavailable, still processing discussions and surfacing relevant context from the local knowledge base.

How are out-of-scope issues handled during AI-assisted triage?

Out-of-scope issues are managed by referencing OUT-OF-SCOPE.md notes during triage, ensuring the AI recognizes boundaries and applies the wontfix state appropriately to invalid requests.