executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
ops-and-buildsChoose MMCV package variants, inspect compiled ops availability, and troubleshoot install, build, CUDA, and backend failures.
Independent GitHub snapshot · Automated classification · Original documentation governs
Use this sub-skill when a task involves installing MMCV, deciding between mmcv and mmcv-lite, checking whether compiled mmcv.ops are available, selecting a wheel or source build, or diagnosing native-extension/CUDA/backend errors.
mmcv.ops APIs.No module named mmcv.ops, No module named mmcv._ext, shared-object load errors, undefined symbols, CUDA kernel errors, or build failures.../media-processing/.../data-transforms/.mmcv.ops belong in ../cnn-model-building/.mmcv-lite when the workflow does not import mmcv.ops and does not need compiled native kernels.mmcv when any compiled op is required; in MMCV 2.x, mmcv is the full package and mmcv-lite is the lite package.import mmcv does not prove that mmcv.ops or mmcv._ext exists.python scripts/check_mmcv_install.py
python scripts/check_mmcv_install.py --require-ops
python scripts/check_mmcv_install.py --require-cuda --require-ops
The checker reports import/package/Torch/CUDA facts, handles missing ops gracefully, and exits nonzero only when a required check fails.