Agent skill · software engineering · pytorch
scrub-issue
Fetch, analyze, reproduce, and minimize GitHub issue reproductions. Use only when the user asks to check whether a GitHub issue reproduces, minimize a GitHub issue's repro, analyze a GitHub bug report, or scrub/triage a GitHub issue for reproducibility. Do not use for standalone reproduction requests without a GitHub issue.
Why this skill is useful
Adds specific commands and workflows for managing GitHub issues that the AI wouldn't reliably generate on its own.
What it needs
Requires gh, python installed locally. About 11k tokens when loaded. Last updated 2026-08-07. 102,253 stars on the source repository.
What this skill does
Minimize Issue Reproduction Fetch a GitHub issue, evaluate whether it has a reasonable repro, check if it still reproduces, and systematically minimize the repro to the smallest possible self-contained script. Tools Assume the current environment is correct and run python directly. Only use conda run -n <env> for version bisection (step 5a) where you need to temporarily use a different environment. Use the Bash tool's timeout parameter to enforce timeouts when running repro scripts. gh issue view <NUMBER> --repo pytorch/pytorch to fetch the issue body gh issue view --comments <NUMBER> --repo pytorch/pytorch to fetch comments python <script> to run repro scripts gh issue comment <NUMBER> --repo pytorch/pytorch --body <BODY> to comment gh issue edit <NUMBER> --repo pytorch/pytorch --add-label <LABEL> to add labels Multiple gh issue edit flags can be combined in a single command (e.g. --add-label "bug,help wanted" --add-assignee "@me"). Prefer batching edits into one command to minimize API calls and reduce the chance of auto-subscribing to notifications. Preserving notification subscription state Modifying an issue (commenting, adding labels) auto-subscribes you to notifications. Use tools/staleissues.py to save and restore subscription state: 1. Before the first modification, save the current state. This can be run in parallel with fetching the issue body/comments, but it must complete before any gh issue edit, gh issue comment, or gh issue close command is executed: 2. After the last modification, restore the saved state — unless the issue was closed (via gh issue close), in which case skip the restore so the user stays subscribed to follow any responses to the closure. The restore must be the very last GitHub API call — do not run it in the background or in parallel with any gh issue edit or gh issue comment commands: If either the save or restore command fails, warn the user and continue without the save/restore mechanism. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills pytorch/scrub-issue