What problem does it solve?
ComfyUI cloud builds frequently fail on dependency conflicts caused by inherited pip freeze pins in comfy-build.yaml, and each failed build costs minutes. This Skill explains which pins to delete, which to keep, and how to predict conflicts from requirements files before spending a build.
Core Features & Use Cases
- Pin triage rules: Identifies lines to always delete (torch, torchvision, torchaudio, triton, xformers, nvidia-*, platform-specific wheels) and rules for pins worth keeping, such as numpy/scipy and opencv-python/opencv-python-headless pairs that must move together.
- Pre-build conflict prediction: Concatenates ComfyUI core and custom node pack requirements.txt files (cloning packs at their pinned gitRef when needed) and resolves them with uv pip compile against the target Python version and manylinux platform tag.
- Failure pattern recognition: Detects three conflict shapes in requirements text — two packages providing one import, a ceiling pin on a shared package, and a pack pinned far below the install's running versions.
- Use Case: Before submitting a comfy-build, clone each declared pack at its pinned ref, concatenate requirements files, strip torch-stack lines, and run uv pip compile with the base image's Python and manylinux_2_34 platform to surface the real blocker without spending a build.
Quick Start
Ask the AI to review the pipDependencies in your comfy-build.yaml and predict any dependency conflicts using the comfy-build-pins reference before starting the build.
