Agent skill · software engineering · pytorch
pr-review
Review PyTorch pull requests for code quality, test coverage, security, and backward compatibility. Use when reviewing PRs, when asked to review code changes, or when the user mentions "review PR", "code review", or "check this PR".
Why this skill is useful
Adds specific commands and workflows for reviewing PyTorch PRs that the AI wouldn't reliably generate on its own.
What it needs
Requires gh installed locally. About 8k tokens when loaded. Last updated 2026-08-07. 102,253 stars on the source repository.
What this skill does
PyTorch PR Review Skill Review PyTorch pull requests focusing on what CI cannot check: code quality, test coverage adequacy, security vulnerabilities, and backward compatibility. Usage Modes No Argument If the user invokes /pr-review with no arguments, do not perform a review. Instead, ask the user what they would like to review: What would you like me to review? - A PR number or URL (e.g., /pr-review 12345) - A local branch (e.g., /pr-review branch) Local CLI Mode The user provides a PR number or URL: For a detailed review with line-by-line specific comments: Use gh CLI to fetch PR data: Local Branch Mode Review changes in the current branch that are not in main: Use git commands to get branch changes: For local branch reviews: The "Summary" should describe what the branch changes accomplish based on commit messages and diff Use the current branch name in the review header instead of a PR number All other review criteria apply the same as PR reviews GitHub Actions Mode When invoked via @claude /pr-review on a GitHub PR, the action pre-fetches PR metadata and injects it into the prompt. Detect this mode by the presence of <formattedcontext>, <prorissuebody>, and <comments> tags in the prompt. The prompt already contains: PR metadata (title, author, branch names, additions/deletions, file count) PR body/description All comments and review comments (with file/line references) List of changed files with paths and change types Use git commands to get the diff and commit history. The base branch name is in the prompt context (look for PR Branch: <head> -> <base> or the baseBranch field). Do NOT use gh CLI commands in this mode -- only git commands are available. All PR metadata, comments, and reviews are already in the prompt context; only the diff and commit log need to be fetched via git. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills pytorch/pr-review