package-management

Convert legacy npm, yarn, and cargo workflows into Pixi-managed execution.

Updated Jan 12, 2026
One-click install
npx skills add https://github.com/drdave-flexnetos/ripple-env --skill package-management-drdave-flexnetos
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: package-management
Source: https://github.com/drdave-flexnetos/ripple-env/tree/main/.claude/skills/package-management
Command: npx skills add https://github.com/drdave-flexnetos/ripple-env --skill package-management-drdave-flexnetos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents broken builds caused by mismatched or conflicting dependencies by enforcing a Pixi-first installation and command workflow across npm, yarn, and cargo ecosystems.

Core Features & Use Cases

  • Pixi-first dependency management: Uses Pixi as the central manager to provide consistent, reproducible environments via lock files.
  • Command conversion rules: Translates legacy npm/yarn/cargo workflows into equivalent pixi run ... patterns (including dlx for one-off executions).
  • Conflict detection and resolution guidance: Helps diagnose common coupling issues like PyTorch/torchvision/torchaudio alignment, Python version constraints, CUDA mismatches, and channel conflicts; supports targeted environment selection (e.g., js/cuda/aios/llmops/docs/ros2).

Example: You need to add a new Node and Rust dependency for a robotics project and avoid environment drift that causes “it works on my machine” failures after reloads.

Quick Start

Convert your installation and build commands to Pixi-run equivalents and verify compatibility by checking the relevant environment-specific dependency and conflict patterns, starting with the Node scope via pnpm.

Frequently Asked Questions about package-management

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I resolve dependency conflicts when switching between npm, yarn, and cargo?▼

Resolve dependency conflicts by converting legacy npm, yarn, and cargo workflows into a Pixi-managed execution model. This enforces consistent, reproducible environments via lock files and prevents broken builds caused by mismatched packages.

How does Pixi handle environment isolation for Python and Node development?▼

Pixi handles environment isolation by acting as the central package manager, wrapping installations and command executions via pixi run. It uses lockfile-driven reproducibility to eliminate environment drift and ensure consistent builds.

Can I use pnpm for one-off executions within a Pixi-managed workflow?▼

Yes, you can use pnpm within a Pixi-managed workflow by running it via pixi dlx for one-off executions. This maintains environment consistency while allowing targeted Node scope dependency management.

What is the best way to fix PyTorch and CUDA version mismatches in reproducible builds?▼

Fix PyTorch and CUDA version mismatches by using Pixi environment selection and solve-group practices. This approach diagnoses common coupling issues like torchvision alignment and Python constraints to ensure reproducible builds.

Does Pixi support managing dependencies across Python, Node, and Rust ecosystems simultaneously?▼

Pixi supports managing dependencies across Python, Node, and Rust ecosystems simultaneously by translating legacy installation workflows into equivalent pixi run patterns. This provides unified lockfile-driven reproducibility for multi-language projects.

Why do my builds break after reloads due to environment drift in robotics projects?▼

Builds break after reloads due to environment drift when dependencies are mismatched. Converting installation and build commands to Pixi-run equivalents verifies compatibility and prevents it works on my machine failures.