triage-issues

Identify unlabeled GitHub issues and route them to a specified team.

127|21|Updated Jan 11, 2016
One-click install
npx skills add https://github.com/haacked/dotfiles --skill triage-issues
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage-issues
Source: https://github.com/haacked/dotfiles/tree/main/ai/skills/triage-issues
Command: npx skills add https://github.com/haacked/dotfiles --skill triage-issues

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the triage of unlabeled GitHub issues, helping engineering teams quickly identify candidates for assignment to the correct team.

Core Features & Use Cases

  • Automated Issue Triage: Detect unlabeled issues and propose team labels for faster routing.
  • Configurable Filters: Apply age (days), limit, and team scope to surface relevant issues.
  • Use Case: Imagine a project with a steady stream of new issues; this Skill surfaces those likely belonging to a specific team for targeted review.

Quick Start

Use this skill to triage unlabeled issues by specifying days, limit, and team as needed, for example: /triage-issues 7 50 web-analytics

Frequently Asked Questions about triage-issues

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

FAQPage Schema
How do I automate triage of unlabeled GitHub issues?

Automating GitHub issue triage involves detecting unlabeled open issues and routing them to the appropriate team. This skill uses the gh CLI to fetch issues within a specified date window and delegates analysis to a subagent for team labeling suggestions.

How do I filter unlabeled GitHub issues by age and team scope?

Filtering unlabeled GitHub issues by age and team scope requires argument parsing for days, limit, and team parameters. You provide these arguments to surface relevant issue candidates for a specific team within your specified date window.

Can I use this automated triage tool with repositories other than PostHog?

This automated triage tool is specifically applied to open issues in the PostHog/posthog repository. It identifies unlabeled issues within that specified date window and surfaces candidates for a given team for targeted review.

What is the best way to route unlabeled GitHub issues to engineering teams?

Routing unlabeled GitHub issues to engineering teams is best handled by fetching issues with label filters using gh, then delegating analysis to a subagent. This proposes team labels for faster routing and assignment.

Do I need the gh CLI to automate GitHub issue labeling and team routing?

Yes, you need the gh CLI to automate GitHub issue labeling and team routing. The skill uses gh to fetch open issues with label filters before delegating the analysis to a subagent for labeling suggestions.