triage

Generate structured briefs and categorize issues and pull requests.

Updated Jun 12, 2026
One-click install
npx skills add https://github.com/flowel/AiSkills --skill triage-flowel
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/flowel/AiSkills/tree/main/skills/codex/triage
Command: npx skills add https://github.com/flowel/AiSkills --skill triage-flowel

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the triage process for issues and pull requests, providing structured briefs and categorization to streamline the workflow.

Core Features & Use Cases

  • Automated Briefs: Generates detailed briefs for issues and PRs, outlining current and desired behaviors, key interfaces, and acceptance criteria.
  • Categorization: Automatically categorizes issues as bugs or enhancements and assigns appropriate states for further action.
  • Use Case: Use this Skill to efficiently manage a large number of issues and PRs, ensuring they are properly categorized and assigned to the correct team members.

Quick Start

Run the triage skill with the command: /triage

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 a large backlog of pull requests?

You can automate issue triage by running the /triage command to generate structured briefs, categorize items as bugs or enhancements, and assign appropriate states for further action.

What is automated PR categorization and how does it streamline workflows?

Automated PR categorization parses issue and PR metadata to classify items as bugs or enhancements, generating detailed structured briefs that outline current behaviors, key interfaces, and acceptance criteria to streamline workflows.

How do I generate automated briefs for issues to outline acceptance criteria?

To generate automated briefs for issues, run the /triage command which parses metadata to produce detailed outlines of current and desired behaviors, key interfaces, and acceptance criteria.

Do I need any external dependencies to categorize issues as bugs or enhancements?

No external dependencies are required to categorize issues as bugs or enhancements; the Skill operates independently using its internal scripts and references to parse and manipulate issue metadata.

What's the best way to manage a large number of pull requests and ensure they are properly assigned?

The best way to manage a large number of pull requests is using automated triage to generate structured briefs and categorize items, ensuring they are properly assigned to the correct team members.