.config/opencode/skills/pyenv-activation/SKILL.md
Guide for activating pyenv virtual environments with troubleshooting for common issues
npx skillsauth add alexismanuel/dotfiles pyenv-activationInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
This skill should be used when activating pyenv virtual environments or troubleshooting pyenv activation issues.
Activate pyenv virtual environments reliably, with fallbacks when standard activation methods fail.
pyenv activate <env-name>
This requires pyenv-virtualenv to be loaded into the shell.
If pyenv-virtualenv is not loaded:
eval "$(pyenv init -)" && eval "$(pyenv virtualenv-init -)" && pyenv activate <env-name>
When pyenv activation fails or shell integration is not enabled, activate the virtual environment directly using its path:
source /Users/alexismanuel/.pyenv/versions/<python-version>/envs/<env-name>/bin/activate
To find the correct path:
pyenv versions to list available environments~/.pyenv/versions/<version>/envs/<env-name>/bin/activate| Error | Cause | Solution |
|-------|-------|----------|
| "pyenv-virtualenv has not been loaded" | pyenv-virtualenv plugin not initialized | Use Method 2 |
| "shell integration not enabled" | pyenv shell integration not configured | Use Method 3 |
| Activation appears to work but wrong Python version | Environment not properly activated | Verify with python --version and which python |
After activation, always verify the environment is active:
python --version
which python
Expected output should show the Python version from the pyenv environment and a path under ~/.pyenv/versions/.
development
Generate GitLab merge request descriptions from git commits with automatic categorization and Jira integration.
development
This skill should be used when validating that an implementation plan was correctly executed. It verifies success criteria, runs tests, identifies deviations, and presents structured completion options including MR creation or discard.
development
This skill should be used when reviewing code changes in a branch against main/master/develop. It analyzes commits, integrates JIRA ticket and MR context when available, and produces a structured code review using Conventional Comments format.
development
This skill should be used when conducting comprehensive codebase research to answer questions, understand architecture, or prepare context for implementation planning. It spawns parallel sub-agents and synthesizes findings into a structured research document.