oss-triage

Classify open GitHub issues, detect duplicates, and apply labels via GitHub CLI.

2|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/jonaseck2/slaktforskning --skill oss-triage
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: oss-triage
Source: https://github.com/jonaseck2/slaktforskning/tree/main/.claude/skills/oss-triage
Command: npx skills add https://github.com/jonaseck2/slaktforskning --skill oss-triage

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It reduces the backlog and confusion of open GitHub issues by automatically categorizing new reports, identifying likely duplicates, and closing redundant threads.

Core Features & Use Cases

  • Duplicate detection workflow: Compares unlabeled issues against existing open and closed issues using title keyword search, then closes confirmed duplicates with a comment pointing to the original.
  • Deterministic labeling: Applies consistent labels based on issue signals (bug, enhancement, question, needs-info), with a fallback for ambiguous reports.
  • Needs-information follow-up: Posts a short, targeted request for the specific details required to reproduce or understand the issue.
  • Operational summary: Produces a concise triage report counting how many issues were closed as duplicates vs. labeled by category.

Quick Start

Ask the AI to triage issues and label/close duplicates for the repository’s open unlabeled GitHub issues using the GitHub CLI.

Frequently Asked Questions about oss-triage

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

FAQPage Schema
How do I automatically triage open GitHub issues and label duplicates?

To automatically triage open GitHub issues, this Skill fetches unlabeled reports via GitHub CLI, searches for duplicates, applies appropriate labels, and closes redundant threads to reduce backlog noise.

How does automated duplicate detection work for GitHub bug reports?

Automated duplicate detection for GitHub bug reports works by comparing unlabeled issues against open and closed entries using title keyword search, then closing confirmed duplicates with a comment pointing to the original.

Can I automatically apply needs-info labels to vague GitHub issues?

Yes, you can automatically apply needs-info labels to vague GitHub issues. This Skill classifies ambiguous reports, applies the needs-info label, and posts targeted comments requesting specific details to reproduce the issue.

What is the best way to organize GitHub issues by type like bug reports and enhancement requests?

The best way to organize GitHub issues by type is using deterministic labeling to classify bug reports, enhancement requests, questions, and vague submissions, reducing backlog confusion while producing an operational summary.

Do I need the GitHub CLI to categorize new GitHub issues automatically?

Yes, you need the GitHub CLI to categorize new GitHub issues automatically. This Skill fetches issue lists, searches candidate duplicates, creates missing labels, and comments on threads via the GitHub CLI.