alekspetrov/navigator/nav-upgrade
Claude Code and agent skill by alekspetrov/navigator
- community
Checking that the SKILL.md file is still in the repository.
Automates Navigator plugin updates. Detects current version, updates plugin, verifies installation, updates project CLAUDE.md, and validates new features. Auto-invoke when user mentions upgrading Navigator or getting new features.
Install
npx vskill@latest install alekspetrov/navigator/nav-upgradeSKILL.md
Navigator Upgrade Skill
Automate Navigator plugin updates with version detection, conflict resolution, and post-update validation.
When to Invoke
Auto-invoke when user says:
- "Update Navigator"
- "Upgrade Navigator plugin"
- "Get latest Navigator version"
- "Update to Navigator v3.3.0"
- "Install new Navigator features"
- "Check for Navigator updates"
What This Does
6-Step Workflow:
- Version Detection: Check current Navigator version vs latest
- Plugin Update: Execute
/plugin update navigator - Verification: Confirm update succeeded
- CLAUDE.md Update: Update project configuration (via nav-sync-claude)
- Hooks Setup: Install/update token monitoring hooks in project
- Feature Discovery: Show new features available
Time Savings: Manual update (10-15 min) → Automated (2 min)
Prerequisites
- Navigator plugin installed
- Project initialized with Navigator
- Internet connection for plugin update
Workflow Protocol
Step 1: Version Detection
Execute: version_detector.py
Check both stable and pre-release versions:
Output scenarios:
Scenario 1: Stable update available
Scenario 2: Pre-release available (user on stable)
Present choice:
Scenario 3: Already on latest (stable or pre-release)
Skip to Step 5 (Feature Discovery).
Scenario 4: On pre-release, newer stable available
Step 2: Plugin Update
Scenario-based update strategy:
Scenario 2: Pre-release Available (User on Stable)
When pre-release detected, present choice using AskUserQuestion tool:
If user chooses [1] (Stay stable):
If user chooses [2] (Try experimental):
Then verify installation:
Scenario 1: Stable Update Available
Execute: /plugin update navigator
Monitor output:
If update fails:
Automatic retry (once): If update fails, try uninstall/reinstall automatically:
Step 3: Verification
Execute: plugin_verifier.py
Verify:
- Plugin version matches latest
- New skills registered in plugin.json
- Skills are invokable
Test new skills (v3.3.0 example):
Output:
If verification fails:
Prompt user to restart Claude Code.
IMPORTANT - Restart Required After All Updates:
Claude Code caches skill paths at session start. Even successful updates require a restart to load new skills:
This is a Claude Code behavior, not a Navigator issue. The plugin files update correctly, but the active session continues using cached skill paths from the old version.
Step 4: Update Project CLAUDE.md (Automatic)
After plugin update, automatically invoke: nav-sync-claude skill
What happens automatically:
- Detects new plugin version (e.g., v4.3.0)
- Fetches matching template from GitHub
- Preserves project customizations
- Updates CLAUDE.md in current project
- Shows diff for review
Template sync benefits:
- ✅ CLAUDE.md always matches installed plugin version
- ✅ No template drift (v4.0 templates with v4.3 plugin)
- ✅ Pre-release templates accessible
- ✅ Offline fallback to bundled templates
User action required:
See: nav-sync-claude skill for details.
Step 5: Migrate Legacy Hooks Out of .claude/settings.json
v6.13.0+: Navigator's lifecycle hooks now ship with the plugin manifest (.claude-plugin/plugin.json's top-level hooks field). Claude Code only substitutes ${CLAUDE_PLUGIN_ROOT} for hooks declared in a plugin manifest, so the prior approach (merging hooks into the project's .claude/settings.json) produced broken commands like /hooks/X.py (empty expansion). Hooks ship with the plugin from v6.13.0 onwards.
For existing installs, the old hook entries are duplicated in .claude/settings.json and must be removed to prevent double-firing:
Behavior:
- Conservative match: command string must contain BOTH
hooks/AND one of
the known Navigator hook names (nav_session_start, nav_pre_compact, nav_post_compact, nav_workflow_state, nav_read_guard, nav_task_graph_sync, nav_profile_sync, nav_commit_reminder, nav_brief, token_monitor, workflow_enforcer).
- Writes a
.pre-migrate.<timestamp>backup before any change. - Logs every removed entry to stderr.
- Idempotent: re-running on an already-migrated file is a no-op.
- Never touches entries with unrelated commands.
Fresh installs do not need this step — they never had hooks in .claude/settings.json to begin with.
v7.0.0 migration note: the nine per-hook scripts were replaced by a single dispatcher (hooks/nav_dispatch.py) routing to hooks/ops/* — the old files no longer exist in the plugin. Any consumer settings.json entry still referencing an old hook path (e.g. hooks/nav_session_start.py, hooks/workflow_enforcer.py, hooks/nav_brief.py) is stale and now fails with "No such file or directory" on every event. Run the same migrate_hooks_out_of_settings.py step above — its basename list covers all nine v6 hooks — then restart Claude Code. Per-hook state files are archived automatically by the SessionStart op to .agent/.nav-v6-state.bak/ (replaced by .agent/.nav-runtime-state.json, schema 2).
Step 6: Post-Upgrade Setup Check
Check if new features require setup:
If setup needed, show instructions:
PLUGIN_DIR="${CLAUDE_PLUGIN_ROOT:-$(cat "${NAVIGATOR_CONFIG_HOME:-${XDG_CONFIG_HOME:-$HOME/.config}/navigator}/plugin-root" 2>/dev/null)}" [ -d "$PLUGIN_DIR/skills" ] || PLUGIN_DIR="$HOME/.claude/plugins/marketplaces/navigator-marketplace" cd "$PLUGIN_DIR/skills/product-design" ./setup.sh
Record setup needed in TodoWrite for tracking.
Step 7: Feature Discovery
Show new features available in updated version.
For v3.3.0 update:
"Set up visual regression for ProfileCard" "Add Chromatic to Button component" "Configure visual tests for Input, Card, Modal"
This is the start of the file. Read the full SKILL.md on GitHub.
Security
- Security scanPassed, 100 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationWarning, 70 of 100Marginal. 1 run. Evaluated 8 months ago.
Source
- SKILL.md in the repositoryCheckingskills/nav-upgrade/SKILL.md
Popularity
- Repository stars
- 160
- Repository forks
- 7
- 7-day trend score
- 25
Stars and forks are for the whole GitHub repository, not this skill alone. Refreshed 27 Mar 2026, 7 months ago.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/alekspetrov/navigator/nav-upgrade)