Skip to content
Back to skills

Fix Symlink Shebang Persistence

ASecurity

Permanently fix shebang issues in symlinked CLI tools that get overwritten by git updates

  • 17 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 9, 2026
code-qualitypythondebugginggit

Works with

  • cli

Security analysis

A100/100

Scanned September 9, 2026

npx -y skills add vamseeachanta/workspace-hub --skill fix-symlink-shebang-persistence --agent claude-code

Installs 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 with every re-scan.

Security grade badge for Fix Symlink Shebang Persistence
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/vamseeachanta-fix-symlink-shebang-persistence/badge)](https://www.skillsdirectory.com/skills/vamseeachanta-fix-symlink-shebang-persistence)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
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.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.