# Triage Issues

Triage open GitHub issues by reviewing unlabeled ones and applying the most appropriate...

- Repository: https://github.com/dyoshikawa/rulesync (1577 stars)
- Category: Git and review
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add dyoshikawa/rulesync --skill triage-issues -g -a claude-code -y`
Codex: `npx skills add dyoshikawa/rulesync --skill triage-issues -g -a codex -y`
Cursor: `npx skills add dyoshikawa/rulesync --skill triage-issues -g -a cursor -y`
Gemini CLI: `npx skills add dyoshikawa/rulesync --skill triage-issues -g -a gemini-cli -y`

## Description

Triage open GitHub issues by reviewing unlabeled ones and applying the most appropriate labels based on their content

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Triage Open Issues

Review all open GitHub issues that currently have no labels and apply the most appropriate labels based on their content.

## Step 1: List Available Labels

Fetch the full list of labels defined in this repository so the triage stays within the known label set:

```bash
gh label list --limit 100
```

Treat this list as the authoritative vocabulary. Do not invent new labels.

## Step 2: Find Unlabeled Open Issues

Fetch all open issues that have no labels attached:

```bash
gh issue list --state open --search "no:label" --limit 100 --json number,title,author,url
```

If the result is empty, report that nothing needs triage and stop.

## Step 3: Gather Context per Issue

For each unlabeled issue, read the description and the discussion so the label choice is grounded in the actual content:

```bash
gh issue view <issue_number>
gh issue view <issue_number> --comments
```

Run these in parallel across issues where practical.

## Step 4: Decide the Labels

For each issue, pick the labels that best describe it. Typical signals:

The rest: https://github.com/dyoshikawa/rulesync/blob/HEAD/.rulesync/skills/triage-issues/SKILL.md