Menu
Install pyenv and the project's pinned Python. Use before the virtualenv skill when the .python-version interpreter is missing.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | pyenv |
| description | Install pyenv and the project's pinned Python. Use before the virtualenv skill when the .python-version interpreter is missing. |
Install pyenv via Homebrew, install the Python pinned in .python-version, and activate it so
the virtualenv skill builds venv/ against the right interpreter.
brew install pyenv
pyenv install "$(cat .python-version)"
eval "$(pyenv init -)"
.python-version already pins the version, so pyenv selects it automatically once the shims are
active. Confirm:
pyenv version
python --version
virtualenv skill, if the pinned Python isn't installed.eval "$(pyenv init -)" to your shell profile
(e.g. ~/.zshrc).brew)Lint roles and playbooks with ansible-lint from the project virtualenv. Run after every change under roles/.
Run ansible-test sanity on module/plugin changes from the project virtualenv. Run after modifying any file under plugins/.
Format Python plugin code with black from the project virtualenv. Run after every edit to a file under plugins/ so it matches the black version CI enforces.
Manage changelog fragments and CHANGELOG.rst with antsibull-changelog from the project virtualenv. Add a fragment per user-facing change; release consumes fragments to cut a version.
Build the collection tarball with ansible-galaxy from the project virtualenv. Local builds verify only; the tag-driven release workflow builds and publishes.
Run a role's molecule scenario from the project virtualenv. Scenarios hit real Cloudflare and double as the role's example playbook; run from the role directory.