triage-issues
Triage open GitHub issues by reviewing unlabeled ones and applying the most appropriate labels based on their content
Profile →npx skills add dyoshikawa/rulesync --skill triage-issues --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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: - `bug` — something is broken or behaves incorrectly. - `enhancement` — a new feature, new tool/feature support, or a capability request. - `documentation`
- Step 1: List Available Labels
- Step 2: Find Unlabeled Open Issues
- Step 3: Gather Context per Issue
- Step 4: Decide the Labels
- Step 5: Apply the Labels
- Step 6: Report
gh label list --limit 100 gh issue list --state open --search "no:label" --limit 100 --json number,title,author,url gh issue view <issue_number> gh issue view <issue_number> --comments gh issue edit <issue_number> --add-label "bug" --add-label "good first issue"
What does the triage-issues skill do?
Triage open GitHub issues by reviewing unlabeled ones and applying the most appropriate labels based on their content
How do I install it?
Run `npx skills add dyoshikawa/rulesync --skill triage-issues --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From dyoshikawa/rulesync, a repository with 1,285 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.