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.