Identify and fix shebang mismatches when CLI tools resolve to system Python instead of their virtual environment
Scanned 9/9/2026
Install to Claude Code
Skills Directorynpx -y skills add vamseeachanta/workspace-hub --skill diagnose-shebang-venv-mismatch --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Diagnose Shebang Venv Mismatch?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/vamseeachanta-diagnose-shebang-venv-mismatch-workspace-hub)More formats (shields.io, HTML) on the badges page.
---
name: diagnose-shebang-venv-mismatch
description: Identify and fix shebang mismatches when CLI tools resolve to system Python instead of their virtual environment
version: 1.0.0
source: auto-extracted
extracted: 2026-04-10
metadata:
tags: ["python", "venv", "debugging", "cli-tools", "shebang"]
---
# Diagnose Shebang vs Venv Mismatch
When a CLI tool fails with ModuleNotFoundError for packages that are installed in its venv, the entry point shebang may be pointing to system Python instead of the venv's Python. Check the shebang in `/usr/local/bin/<tool>` or `~/.local/bin/<tool>` — it should reference the venv's Python (`/path/to/venv/bin/python3`), not `/usr/bin/env python3`. Update the shebang directly or check if the tool's update process regenerates it with a generic shebang, requiring a permanent fix strategy.Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Ultra-compressed commit message generator. Cuts noise from commit messages while preserving intent and reasoning. Conventional Commits format. Subject ≤50 chars, body only when "why" isn't obvious. Use when user says "write a commit", "commit message", "generate commit", "/commit", or invokes /caveman-commit. Auto-triggers when staging changes.
