github-triage

Fetches open GitHub issues, classifies them, and appends untracked items to BACKLOG.md.

Updated May 2, 2026
One-click install
npx skills add https://github.com/whinchman/midi-man-mk3 --skill github-triage-whinchman
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-triage
Source: https://github.com/whinchman/midi-man-mk3/tree/main/.claude/skills/github-triage
Command: npx skills add https://github.com/whinchman/midi-man-mk3 --skill github-triage-whinchman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Open GitHub issues pile up without being reflected in the project backlog, forcing maintainers to manually compare issue trackers against planning files and decide where each item belongs. ## Core Features & Use Cases - Issue Discovery and Deduplication: Fetches open issues via the GitHub CLI and skips any already tracked in BACKLOG.md, TODO.md, or DONE.md by matching [GH #N] markers. - Reasoned Classification: Categorizes each untracked issue as Feature, Change, or Issue based on its language, and skips questions, duplicates, excluded labels, and out-of-scope items. - Backlog Population: Appends formatted checkbox entries with one-line summaries to the correct BACKLOG.md section, or delegates to a GitHub Projects board when workflow.backend is github_project. - Use Case: After a community files a dozen new issues on your repository, run this Skill to triage them into the backlog in one pass and receive a report of what was added, skipped, and already tracked. ## Quick Start Ask the agent to triage open GitHub issues for this repository and add any untracked ones to the backlog.

Frequently Asked Questions about github-triage

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

FAQPage Schema
How do I triage GitHub issues into a project backlog automatically?▼

Run the github-triage Skill, which fetches open issues with the GitHub CLI, filters out already-tracked ones by scanning for [GH #N] markers, classifies each as Feature, Change, or Issue, and appends formatted entries to BACKLOG.md.

How does the triage agent avoid adding duplicate issues to the backlog?▼

It reads BACKLOG.md, TODO.md, and DONE.md and builds a set of issue numbers from [GH #N] markers. Any open issue whose number appears in those files is counted as already tracked and skipped.

Can I exclude certain GitHub issues from triage by label?▼

Yes. Add a github.exclude_labels list to agent.yaml with the label names to skip. Issues carrying any of those labels are automatically excluded, along with questions, duplicates, and out-of-scope items.

What happens if the GitHub CLI is not authenticated?▼

The Skill checks gh auth status during pre-flight. If authentication fails, it stops and reports that you must run gh auth login before triage can proceed.

Does github-triage work with GitHub Projects boards instead of markdown files?▼

Yes. Set workflow.backend to github_project in agent.yaml and the Skill delegates tracking to the board-man agent, which creates board issues with [GH #N] markers and sets their status to BACKLOG.