versionlisted

# Version — show installed iEvo version and changelog Answers "which iEvo version am I running, and what would I gain by updating?" from inside the session — no manual poking at the plugin cache directory. Reports the installed version (and commit SHA when it can be determined), the latest published version, and — when behind — the `CHANGELOG.md` entries for every release in between so the user can decide whether updating is worth it. This complements the passive SessionStart version-check nudge (`hooks-setup` Step 5.7): that nudge only whispers "you're behind" once a day and only if the user opted into hooks. This skill is the on-demand, interactive answer — the full version + changelog, whenever asked. ## When to use - User asks "which iEvo version am I on", "what version is installed", "am I up to date", "how far behind is iEvo", "what changed since my version", "show the iEvo changelog", "what would `/plugin update` give me". - Before deciding whether to update — see the concrete list of changes first. - Onboarding / debugging — confirm exactly which iEvo build is active in this session. ## Steps ### 1. Resolve the installed version (+ commit SHA, best-effort) The skill runs *inside* the plugin, so `CLAUDE_PLUGIN_ROOT` points at the installed plugin directory (same resolution `hooks-setup` Step 5.7.2 relies on). Read the installed version from its manifest: ```sh jq -r '.version // empty' "${CLAUDE_PLUGIN_ROOT}/.claude-plugin/plugin.json" 2>/dev/null ``` If this