Skill
pr-review
Priority: P1 (High — catches common PR errors before CI)
Motivation
Kernel PRs frequently have subtle errors that pass CI but cause runtime failures or documentation drift: parameter names that don't match function signatures, dtype support claims that aren't implemented, missing boundary checks for edge-case shapes, and import paths that reference internal Triton functions instead of exported APIs. A skill automates these checks, catching errors that human reviewers often miss.
What This Skill Should Do
- Signature validation: For every function call in the PR diff, verify parameter names match the actual
def signature (catches common mistakes like fc1_scale vs w1_scale, residual vs res)
- Dtype claim verification: If PR claims support for new dtypes (FP8, FP4, BF16), verify the kernel actually handles those types (check dispatch logic, not just docstrings)
- Boundary condition checks: Verify the kernel handles edge cases — M=1 (single token), non-aligned shapes, empty inputs, shapes where N < BLOCK_N
- Import path validation: Check that
from aiter import X paths reference actual exports in __init__.py, not internal modules
- Documentation consistency: If PR modifies function signatures, check if corresponding docs/ guides need updating
Acceptance Criteria
Skill
pr-reviewPriority: P1 (High — catches common PR errors before CI)
Motivation
Kernel PRs frequently have subtle errors that pass CI but cause runtime failures or documentation drift: parameter names that don't match function signatures, dtype support claims that aren't implemented, missing boundary checks for edge-case shapes, and import paths that reference internal Triton functions instead of exported APIs. A skill automates these checks, catching errors that human reviewers often miss.
What This Skill Should Do
defsignature (catches common mistakes likefc1_scalevsw1_scale,residualvsres)from aiter import Xpaths reference actual exports in__init__.py, not internal modulesAcceptance Criteria