comet-github-issue-triage

Validates and classifies Comet GitHub issues against repository contracts and source code.

2.9k|284|Updated May 14, 2026
One-click install
npx skills add https://github.com/rpamis/comet --skill comet-github-issue-triage
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: comet-github-issue-triage
Source: https://github.com/rpamis/comet/tree/main/assets/skills-maintainer/comet-github-issue-triage
Command: npx skills add https://github.com/rpamis/comet --skill comet-github-issue-triage

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintainers receive GitHub issues that may be duplicates, already implemented, configuration mistakes, or genuine defects, and manually verifying each report against the current codebase is slow and error-prone. This Skill systematically checks each issue against the repository contract, source code, runtime behavior, tests, and installation paths to produce an evidence-based classification.

Core Features & Use Cases

  • Evidence-Based Verification: Reads the full issue thread, searches for duplicates by domain concept, and inspects current source code, configuration, and tests before judging validity.
  • Structured Classification: Assigns one primary category such as confirmed defect, likely defect, configuration/install issue, duplicate/already implemented, insufficient information, or feature request.
  • Actionable Triage Reports: Returns classification with confidence level, examined evidence, relevant code paths, and recommended next steps without auto-closing, labeling, or commenting.
  • Use Case: A maintainer receives a bug report claiming broken installation behavior. The Skill checks the current install paths and tests, determines the report stems from an outdated local setup, and classifies it as a configuration/install issue with supporting evidence.

Quick Start

Ask the assistant to verify and classify a specific Comet GitHub issue using the comet-github-issue-triage skill, providing the issue number or link.

Frequently Asked Questions about comet-github-issue-triage

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

FAQPage Schema
How do I triage GitHub issues against a repository's source code?

Read the full issue thread, search existing issues by domain concept rather than exact wording, then inspect current source code, configuration, and tests. Classify the report as a confirmed defect, configuration issue, duplicate, or feature request based on the evidence found.

How to tell if a GitHub bug report is a configuration issue?

Compare the reported behavior against the current installation paths, generated assets, and tests in the repository. If the product behaves according to its contract and the problem traces to an outdated local install or misconfiguration, classify it as a configuration/install issue.

Can this skill automatically close or label GitHub issues?

No. The skill is explicitly read-only and never closes, labels, comments on, or creates issues automatically. It only returns a classification with evidence and recommended actions, and any follow-up issue drafting requires explicit user confirmation.

What issue categories does the triage workflow produce?

It assigns one primary category: confirmed defect, likely defect, configuration/install issue, duplicate/already implemented, insufficient information, or feature request. Each result includes a confidence level, examined evidence, and suggested next steps.

Why does issue triage require reading the maintainer contract first?

The maintainer contract defines the repository's expected behavior and boundaries, serving as the authoritative baseline for judgment. Without it, a report that merely sounds plausible could be misclassified as a defect when it actually reflects intended behavior.