Agent skill · operations · pytorch
triaging-issues
Triages GitHub issues by routing to oncall teams, applying labels, and closing questions. Use when processing new PyTorch issues or when asked to triage an issue.
Why this skill is useful
Adds 3 executable scripts for validating issue targets, labels, and automating triage actions that are not publicly documented.
What it needs
Requires python3 installed locally. About 10k tokens when loaded. Last updated 2026-08-07. 102,253 stars on the source repository.
What this skill does
PyTorch Issue Triage Skill This skill helps triage GitHub issues by routing issues, applying labels, and leaving first-line responses. Contents MCP Tools Available Labels You Must NEVER Add Issue Triage Steps Step 0: Already Routed — SKIP Step 1: Question vs Bug/Feature Step 1.5: Needs Reproduction — External Files Step 2: Transfer Step 2.5: PT2 Issues — Special Handling Step 3: Redirect to Secondary Oncall Step 4: Label the Issue Step 5: Escalate — High Priority (human review), then release triage Step 6: bot-triaged (automatic) Step 7: Mark Triaged V1 Constraints Labels reference: See labels.json for the full catalog of labels suitable for triage. ONLY apply labels that exist in this file. Do not invent or guess label names. This file excludes CI triggers, test configs, release notes, deprecated labels, and labels requiring human decision. PT2 triage guide: See pt2-triage-rubric.md for detailed labeling guidance when triaging PT2/torch.compile issues. Response templates: See templates.json for standard response messages. --- MCP Tools Available Use these GitHub MCP tools for triage: Tool Purpose ------ --------- mcpgithubgetissue Get issue details and existing labels mcpgithubgetissuecomments Get existing issue comments mcpgithubupdateissue Apply labels or close issues mcpgithubaddissuecomment Add comment (only for redirecting questions) mcpgithubsearchissues Find similar issues for context --- Labels You Must NEVER Add Prefix/Category Reason ----------------- -------- Labels not in labels.json Only apply labels that exist in the allowlist ciflow/ CI job triggers for PRs only test-config/ Test suite selectors for PRs only release notes: Auto-assigned for release notes ci-, ci: CI infrastructure controls sev Severity labels require human decision merge blocking Requires human decision actionable, needs design, needs reproduction, needs research Reserved for human reviewers after they have reviewed the issue Any label containing "deprecated" Obsolete oncall: releng …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills pytorch/triaging-issues