What problem does it solve? ImageNet eval preprocessing has a silent trap: Resize(256) (int, short-side) and Resize((256, 256)) (tuple, square) extract different patches from non-square images, so top-k activating images, neuron labels, and interpretability scores silently diverge between pipelines that look identical. ## Core Features & Use Cases - Drop-in transform: Provides a canonical imagenet_eval_transform (square 256x256 resize, 224 center crop, ImageNet mean/std) ready to paste into any Dataset/DataLoader. - Convention comparison: Documents when to use square resize, classic ResNet short-side 256, torchvision V2 (232), or CLIP preprocessing, so the choice is intentional rather than accidental. - Audit workflow: Supplies grep commands and decision rules for reviewing an existing repo's torchvision.transforms / PIL pipeline and patching misapplied resizes. - Use Case: While collecting hooked activations from a frozen ResNet backbone, you notice top-k activating images differ from a colleague's run; this Skill identifies the int-vs-tuple Resize mismatch and unifies both pipelines. ## Quick Start Ask the assistant to audit my experiment's torchvision preprocessing pipeline and align it with the canonical ImageNet eval transform.