skill: add triage-issues for labeling open issues - #902
Open
Aditya Shantanu (aditya-shantanu) wants to merge 1 commit into
Open
skill: add triage-issues for labeling open issues#902Aditya Shantanu (aditya-shantanu) wants to merge 1 commit into
Aditya Shantanu (aditya-shantanu) wants to merge 1 commit into
Conversation
Adds a skill that agents can invoke (via "triage issues") to classify open GitHub issues with the correct kind/, area/, and prio/ labels. The skill: - Documents the full label taxonomy with clear when-to-apply rules - Adds two missing labels: kind/design (design discussions / investigations before implementation) and area/benchmarking (the repo has a benchmarking/ directory with no corresponding area label) - Prioritizes unlabeled issues, then reviews labeled issues for gaps - Uses --add-label so existing human-applied labels are never overwritten - Includes a classification guide with decision questions and real examples drawn from the current issue backlog - Outputs a report table of what was changed, plus flagged uncertainties Of 202 open issues, 13 are currently unlabeled. Several labeled issues also lack a kind/ label or use kind/feature for what are really design discussions.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed and why
Adds
.agents/skills/triage-issues/SKILL.md— a skill agents invoke (via "triage issues") to classify open GitHub issues with the correctkind/,area/, andprio/labels.Of 202 open issues, 13 are currently unlabeled. Several labeled issues also lack a
kind/label or usekind/featurefor what are really design discussions.What the skill does
--add-label(not--label) so existing human-applied labels are never overwrittenwontfix/duplicate/invalid— those stay with maintainersTwo new labels proposed
The current taxonomy has two gaps I found while analyzing the backlog:
kind/design— Several issues are design discussions or investigations that must be resolved before any code is written (e.g. "Design discussion: WorkerPool vs. node-level Actor runtime", "Identify what metrics to use for HPA autoscaling", "Measure atenet-router request capacity"). These are currently unlabeled or mislabeled askind/feature. The skill creates this label if it doesn't exist.area/benchmarking— The repo has a fullbenchmarking/directory but no corresponding area label. Performance measurement issues have nowhere to go. The skill creates this label if it doesn't exist.Checklist
go test ./...)hack/run-root-tests.sh)