Skill file goes stale after pip upgrade — no re-install prompt or automation

[skoodster]

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:

1. Post-install hook — graphify install runs automatically after pip install --upgrade graphifyy (via setuptools entry point or similar)
2. 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.
3. 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

[safishamsi]

Fixed in v0.3.10. graphify install now writes a .graphify_version stamp alongside the skill file. Every graphify command checks all platform skill locations and warns if stale. Run graphify install to update.