pypi-collision-fix

PyPI package name collisions occur when your local package shares a name with a PyPI package, causing pip to download the wrong version during editable installs. This Skill resolves collisions by implementing direct package name installations and bypassing the package[extra] syntax to keep your local development version active.

When installing optional dependencies using extras syntax (package[extra]), pip may resolve to a PyPI package instead of your local version if a name collision exists. This Skill fixes it by enforcing direct package installations that bypass extras resolution, ensuring your local package remains active.

Yes. This Skill handles extras resolution conflicts (bio, gpu, etc.) by updating CLI and workflow logic to use direct package name installations instead of the package[extra] syntax, preventing PyPI from overwriting your local development version.

Use direct package installation when your local package name exists on PyPI and you're using editable installs with optional dependencies. This approach prevents silent package conflicts where pip pulls from PyPI instead of your local development version.

Regular pip dependency management handles version conflicts; collision fixing addresses a specific failure mode where local and PyPI package names collide, causing pip to silently install the wrong package. This Skill prevents that by enforcing local package precedence.