Problem
graphify install copies a platform-specific skill file (e.g. skill-windows.md) to ~/.claude/skills/graphify/SKILL.md. After pip install --upgrade graphifyy, the package's skill files are updated but the installed copy at ~/.claude/skills/ is stale. There is no warning, no version check, and no post-install hook to re-sync.
Users have no way to know the skill is out of date unless they manually diff or remember to re-run graphify install after every upgrade.
Current behavior
pip install --upgrade graphifyy # package skill files updated
# ~/.claude/skills/graphify/SKILL.md still has the old version — no warning
Expected behavior
One or more of:
- Post-install hook —
graphify install runs automatically after pip install --upgrade graphifyy (via setuptools entry point or similar)
- Version stamp in the skill file — Embed the graphify version in the installed SKILL.md. On
/graphify invocation, the skill can compare against the installed package version and warn if stale.
- Upgrade check in CLI —
graphify install could print a reminder after upgrade, or graphify itself could warn when the installed skill version doesn't match the package version.
Option 2 seems lightest — stamp the version at copy time, add a check at the top of the skill that compares graphify.__version__ against the stamped version.
Environment
- graphifyy v0.3.9
- Windows 11, Python 3.14
graphify install correctly auto-detects Windows and copies skill-windows.md
Problem
graphify installcopies a platform-specific skill file (e.g.skill-windows.md) to~/.claude/skills/graphify/SKILL.md. Afterpip install --upgrade graphifyy, the package's skill files are updated but the installed copy at~/.claude/skills/is stale. There is no warning, no version check, and no post-install hook to re-sync.Users have no way to know the skill is out of date unless they manually diff or remember to re-run
graphify installafter every upgrade.Current behavior
Expected behavior
One or more of:
graphify installruns automatically afterpip install --upgrade graphifyy(via setuptools entry point or similar)/graphifyinvocation, the skill can compare against the installed package version and warn if stale.graphify installcould print a reminder after upgrade, orgraphifyitself could warn when the installed skill version doesn't match the package version.Option 2 seems lightest — stamp the version at copy time, add a check at the top of the skill that compares
graphify.__version__against the stamped version.Environment
graphify installcorrectly auto-detects Windows and copiesskill-windows.md