comphead commented on code in PR #4109: URL: https://github.com/apache/datafusion-comet/pull/4109#discussion_r3149127429
########## .claude/skills/bug-triage/SKILL.md: ########## @@ -0,0 +1,173 @@ +--- +name: bug-triage +description: Triage open Comet issues marked `requires-triage` per the project bug triage guide. Applies the recommended priority and area labels (and `good first issue` where appropriate), removes `requires-triage`, and files a dated summary issue listing what was done. A human reviews the summary issue and closes it when satisfied. +--- + +Run a bug triage pass for the `apache/datafusion-comet` repository. + +## Overview + +This skill triages every open issue carrying the `requires-triage` label. For +each one it: + +1. Decides a priority and area labels using the project's triage guide. +2. Applies those labels via `gh`. +3. Removes the `requires-triage` label. +4. Records the decision (with rationale) in a single dated summary issue. + +A human reviewer reads the summary issue, sanity-checks the calls, and closes +it when satisfied. Any label correction is done by the reviewer directly on the +affected issue. + +The triage criteria come from the project's own guide. Read it before doing any +classification work; do not rely on memory. + +## Step 1: Read the Triage Guide + +Read the canonical guide in this repository: + +``` +docs/source/contributor-guide/bug_triage.md +``` + +Use the priority decision tree, escalation triggers, area labels, and +prioritization principles from that guide. If the guide and this skill ever +disagree, the guide wins. Do not paraphrase the guide; quote the labels and +criteria verbatim when classifying. + +## Step 2: Gather Issues That Need Triage + +Fetch all open issues labeled `requires-triage`: + +```bash +gh issue list \ + --repo apache/datafusion-comet \ + --label requires-triage \ + --state open \ + --limit 200 \ + --json number,title,author,createdAt,labels,body,url +``` + +If the list is empty, stop and tell the user there is nothing to triage. Do not +file an empty summary issue and do not modify any labels. + +## Step 3: Classify Each Issue + +For each issue, review the title and body and determine: + +1. **Priority label** (exactly one): apply the decision tree from the guide. + - `priority:critical` if it could produce silent wrong results Review Comment: should we say correctness issues? what about security issues? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
