triage

Categorize GitHub issues, assign priority, and recommend maintainer-approved actions.

3|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/Abhilash-003/mstack --skill triage-abhilash-003
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/Abhilash-003/mstack/tree/main/triage
Command: npx skills add https://github.com/Abhilash-003/mstack --skill triage-abhilash-003

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It reduces maintainer time spent on issue backlog work by automatically drafting a consistent triage plan—categorizing issues, spotting likely duplicates, and flagging probable bots or spam—while keeping the maintainer in control of every change.

Core Features & Use Cases

  • Issue categorization: Assigns one of bug, feature, enhancement, docs, question, or security based on title/body intent.
  • Priority assessment: Determines critical/high/medium/low to guide how urgently maintainers should respond.
  • Duplicate detection (optional): Compares new issues against all existing issues to identify likely semantic duplicates.
  • Bot/spam heuristics (optional): Uses account signals and issue content to recommend a bot suspicion level, only escalating to maintainer review at high confidence.
  • Completeness scoring: Marks whether the report is actionable or needs more information.
  • Human-approved actions: Produces a triage report and requires explicit user approval before applying labels, commenting, closing duplicates, or flagging items.

Quick Start

Run triage for the open issues in your configured repository by telling Claude: "triage the issues in this repo".

Frequently Asked Questions about triage

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

FAQPage Schema
How do I automatically triage GitHub issues and assign priority labels?

To automatically triage GitHub issues, this Skill categorizes open issues by intent, assesses priority levels, and drafts a maintainer-approved triage plan. It requires GitHub CLI access and repository configuration via .mstack/config.yml before executing any approved gh issue edits or comments.

What is the best way to detect duplicate GitHub issues in a repository backlog?

Duplicate issue detection compares new GitHub issues against existing ones to identify semantic matches. This duplicate detection mechanism is optional and runs during the triage process, recommending maintainer-approved actions like closing duplicates only after explicit user approval.

How can I identify bot or spam issues in my GitHub repository?

Bot and spam detection uses account signals and issue content to assess suspicion levels for GitHub issues. The triage automation only escalates issues to maintainer review at high confidence, filtering probable bots while keeping human control over all flagging actions.

Do I need GitHub CLI installed to categorize and label open issues?

Yes, GitHub CLI access is required to triage open issues, categorize them as bug or feature, and apply maintainer-approved labels. The Skill executes approved gh issue edits, comments, and closes while generating an audit log at .mstack/logs/triage-YYYY-MM-DD.jsonl.

How does issue completeness scoring work for backlog management?

Completeness scoring marks whether a GitHub issue report is actionable or needs more information during triage. This assessment runs alongside issue categorization and priority assignment, helping maintainers quickly identify incomplete reports requiring further details from submitters.

What happens when triage automation flags issues already labeled by category?

Triage automation filters out GitHub issues already labeled by category, skipping them during the categorization process. This prevents redundant labeling and focuses the maintainer workflow on untriaged issues requiring priority assessment, duplicate detection, and bot suspicion evaluation.