First read ../comet-github/references/maintainer-contract.md. Unless the user explicitly authorizes GitHub or code changes, remain read-only.
Gather current evidence
- Read the full Issue body, comments, labels, author, timing, linked PRs, and prior triage records.
- Search existing Issues by domain concept rather than only reusing the reporter's original wording. Identify duplicates, superseded Issues, and already implemented behavior.
- Check the current source code, configuration, installation paths, generated assets, and related tests, using the actual repository contract as the basis for judgment.
- When Bug information is sufficient, reproduce the minimal effective path. Environment or credential issues require distinguishing local setup from product behavior.
Do not assume a defect exists just because the description sounds reasonable. Reports may be valid, exaggerated, outdated, or caused by local installation/configuration inconsistencies.
Classification results
Choose one primary classification:
confirmed defect: The current behavior violates user-visible behavior or the repository contract, and the evidence can pinpoint the path;likely defect: The evidence is strong, but reproduction or a decisive boundary is still missing;configuration/install issue: The product behavior is correct, or the local installation is outdated/misconfigured;duplicate/already implemented: The behavior or Issue already exists elsewhere;insufficient information: Specific steps, versions, logs, platform, or project status need to be added;feature request: The request is for a new capability, not a regression issue.
Report and next steps
Return the classification and confidence, evidence checked, relevant code/Runtime paths, what has been confirmed and what remains unknown, and recommended actions: add information, fix locally, create a focused follow-up, link an existing PR, or handle as duplicate/already implemented.
Do not automatically close, label, comment, or create a follow-up Issue. When a new Issue is truly needed, after the user confirms the scope, hand it off to comet-github-idea-to-issue for drafting.