Alison Aquinas logoAlison's LLM Plugins

pipenv

Included in pluginci-cdView on GitHub ↗

Files

SKILL.mdagentsreferences

Install

Install the containing plugin
/plugin install ci-cd@llm-skills
Invoke this skill after installation
/ci-cd:pipenv
Download pipenv-skill.zip
This skill is bundled inside ci-cd. Install the plugin once, then Claude Code can use any of its included skills. Browse the full plugin repository at github.com/alisonaquinas/llm-ci-dev.

SKILL.md


name: pipenv description: Manage Python virtual environments and dependencies with Pipenv. Use when tasks mention pipenv commands, Pipfile, Pipfile.lock, virtual environment activation, or deterministic installs.

Pipenv

Intent Router

RequestReferenceLoad When
Install tool, first-time setup, Python version selectionreferences/install-and-setup.mdInstall Pipenv or configure the environment
Pipfile format, version specifiers, lock filereferences/pipfile-and-lockfile.mdConfigure Pipfile or understand lock file behavior
CLI commands, workflowsreferences/command-cookbook.mdRun install/sync/lock/check operations
Environment variables, .env loading, venv locationreferences/environment-management.mdControl venv placement or load environment variables

Quick Start

# Install packages (creates Pipfile and venv)
pipenv install requests

# Activate virtual environment shell
pipenv shell

# Run command in environment
pipenv run python app.py

# Install from Pipfile.lock (deterministic)
pipenv sync

Core Command Tracks

  • Install package: pipenv install requests — adds to [packages], creates venv if absent
  • Install dev package: pipenv install --dev pytest — adds to [dev-packages]
  • Activate shell: pipenv shell — spawns a subprocess with the venv activated
  • Run one-off command: pipenv run python app.py — without activating the shell
  • Deterministic install: pipenv sync — installs exactly what is in Pipfile.lock
  • Regenerate lock file: pipenv lock — resolves dependencies and writes Pipfile.lock
  • Security audit: pipenv check — checks installed packages against known vulnerabilities
  • Dependency graph: pipenv graph — prints the full dependency tree

Safety Guardrails

  • Set PIPENV_VENV_IN_PROJECT=1 to place the virtual environment inside the project directory for portability and easier cleanup.
  • Commit Pipfile.lock to version control to ensure reproducible installs in CI and on other machines.
  • Use pipenv check regularly to surface security vulnerabilities in installed packages.
  • Avoid running pip install directly inside a Pipenv-managed environment — use pipenv install to keep Pipfile and the lock file in sync.

Workflow

  1. Run pipenv install <package> to add runtime dependencies.
  2. Run pipenv install --dev <package> to add development-only dependencies.
  3. Run pipenv lock after manual edits to Pipfile to regenerate the lock file.
  4. Run pipenv sync in CI to install the exact locked versions.
  5. Commit both Pipfile and Pipfile.lock.
# Troubleshoot environment issues: verify the venv path and check for conflicts
pipenv --venv
pipenv check
pipenv graph

Related Skills

  • poetry — alternative tool using pyproject.toml with build and publish support
  • pip — lower-level package installer used by Pipenv under the hood
  • ci-architecture — integrating Pipenv into CI/CD pipelines

References

← Back to marketplace