Troubleshoot ModuleNotFoundError in CLI tools by identifying shebang-venv mismatches
Scanned 9/9/2026
Install to Claude Code
Skills Directorynpx -y skills add vamseeachanta/workspace-hub --skill diagnose-shebang-venv-import-errors --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Diagnose Shebang Venv Import Errors?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/vamseeachanta-diagnose-shebang-venv-import-errors)More formats (shields.io, HTML) on the badges page.
---
name: diagnose-shebang-venv-import-errors
description: Troubleshoot ModuleNotFoundError in CLI tools by identifying shebang-venv mismatches
version: 1.0.0
source: auto-extracted
extracted: 2026-04-10
metadata:
tags: ["python", "venv", "debugging", "cli-tools"]
---
# Diagnose Shebang vs Virtual Environment Import Errors
When a CLI tool fails with ModuleNotFoundError despite the package being installed, check if the shebang in `/usr/local/bin/` or `~/.local/bin/` points to system Python instead of the venv Python. Verify the actual Python interpreter being used by examining the shebang (`#!/usr/bin/env python3` vs `/path/to/venv/bin/python3`). If mismatched, update the shebang to explicitly point to the venv's Python executable. Be aware that auto-update mechanisms may revert custom shebangs—check for post-install scripts that regenerate entry points.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.
