triage

Classify software issues and pull requests using a predefined state model.

45|2|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/hachej/boring-ui --skill triage-hachej
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/hachej/boring-ui/tree/main/.agents/skills/triage
Command: npx skills add https://github.com/hachej/boring-ui --skill triage-hachej

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the inconsistency and overhead associated with manual issue and pull request triage by enforcing a standardized state model and clear communication path.

Core Features & Use Cases

  • State Classification: Applies a consistent Boring state model to incoming issues and PRs.
  • Action Tracking: Records the next required action and identifies blockers to ensure progress.
  • Use Case: A maintainer can use this skill to quickly process a backlog of GitHub issues, ensuring every item is categorized, blocked items are identified, and the next steps are clearly documented for the team.

Quick Start

Use the triage skill to analyze the current issue and provide the required state and next action.

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 backlog of GitHub pull requests and issues?

You can automate issue triage by applying a predefined state model and blocker vocabulary to classify development items. The skill analyzes issue content, comments, and linked documentation to document next steps and identify dependencies automatically.

What is the best way to standardize project management state classification for incoming issues?

Standardizing state classification involves applying a consistent state model to incoming issues and pull requests. This approach ensures every item is categorized consistently, blocked items are identified, and next steps are clearly documented for the team.

How does issue tracking automation identify blockers and next actions?

Issue tracking automation identifies blockers by analyzing issue content, comments, and linked documentation using a predefined blocker vocabulary. It then records the next required action and identifies dependencies to ensure continuous project progress.

Can I use this triage automation to process a large backlog of GitHub issues efficiently?

Yes, you can use triage automation to quickly process a backlog of GitHub issues. Maintainers can categorize items, identify blocked tasks, and document next steps, ensuring consistent project tracking across a large backlog.

Does the triage workflow request human input when analyzing pull requests?

Yes, the triage workflow requests human input when necessary during pull request analysis. It facilitates project management by documenting next steps, identifying dependencies, and escalating to human input when automated classification requires clarification.