Review PR

Use this skill to review a change in staged passes. Do not use subagents or tmux unless the user explicitly asks for them.

Ground Rules

Pull the artifact first: read the PR, commit, diff, log, or files under review before forming conclusions.
After the artifact is read, load only the relevant repo skills for the touched areas, such as linting-and-formatting, testing, adding-model-support, build-and-dependency, cicd, or a performance skill.
Preserve user changes. Do not edit files during a review unless the user asks for fixes.
Do not modify 3rdparty/Megatron-LM/. If the reviewed change touches it, flag that boundary.
Do not run the full test suite. Run only targeted checks, using uv run python -m pytest or the repo-approved command form.
Prefer findings with concrete file and line evidence. Drop low-confidence or purely stylistic comments unless the user asks for a strict style pass.

Apply these principles to implementation, APIs, recipes, tests, examples, and documentation. They are acceptance criteria, not optional polish.