pipenv
Files
SKILL.mdagentsreferences
Install
Install the containing plugin
/plugin install ci-cd@llm-skills
Invoke this skill after installation
/ci-cd:pipenv
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
| Request | Reference | Load When |
|---|---|---|
| Install tool, first-time setup, Python version selection | references/install-and-setup.md | Install Pipenv or configure the environment |
| Pipfile format, version specifiers, lock file | references/pipfile-and-lockfile.md | Configure Pipfile or understand lock file behavior |
| CLI commands, workflows | references/command-cookbook.md | Run install/sync/lock/check operations |
| Environment variables, .env loading, venv location | references/environment-management.md | Control 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 inPipfile.lock - Regenerate lock file:
pipenv lock— resolves dependencies and writesPipfile.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=1to place the virtual environment inside the project directory for portability and easier cleanup. - Commit
Pipfile.lockto version control to ensure reproducible installs in CI and on other machines. - Use
pipenv checkregularly to surface security vulnerabilities in installed packages. - Avoid running
pip installdirectly inside a Pipenv-managed environment — usepipenv installto keepPipfileand the lock file in sync.
Workflow
- Run
pipenv install <package>to add runtime dependencies. - Run
pipenv install --dev <package>to add development-only dependencies. - Run
pipenv lockafter manual edits toPipfileto regenerate the lock file. - Run
pipenv syncin CI to install the exact locked versions. - Commit both
PipfileandPipfile.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.tomlwith build and publish support - pip — lower-level package installer used by Pipenv under the hood
- ci-architecture — integrating Pipenv into CI/CD pipelines
References
references/install-and-setup.mdreferences/pipfile-and-lockfile.mdreferences/command-cookbook.mdreferences/environment-management.md- Official docs: https://pipenv.pypa.io/en/latest/
- Pipfile spec: https://github.com/pypa/pipfile
- Security scanning: https://pipenv.pypa.io/en/latest/advanced/#detection-of-security-vulnerabilities