Permanently fix shebang issues in symlinked CLI tools that get overwritten by git updates
Scanned 9/9/2026
Install to Claude Code
npx -y skills add vamseeachanta/workspace-hub --skill fix-symlink-shebang-persistence --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Fix Symlink Shebang Persistence?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/vamseeachanta-fix-symlink-shebang-persistence)More formats (shields.io, HTML) on the badges page.
---
name: fix-symlink-shebang-persistence
description: Permanently fix shebang issues in symlinked CLI tools that get overwritten by git updates
version: 1.0.0
source: auto-extracted
extracted: 2026-04-10
metadata:
tags: ["debugging", "symlinks", "cli-tools", "python", "venv"]
---
# Fix Symlink Shebang Persistence
When a symlink points to a git-tracked repo file with a generic shebang (e.g., `#!/usr/bin/env python3`), edits get overwritten on `git pull`. Instead of editing the repo file, repoint the symlink to the venv's generated entry point (e.g., `~/.venv/bin/hermes`), which has the correct venv-specific shebang and isn't git-tracked. Use `ln -sf <new-target> <symlink>` to update the symlink target.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.