alekspetrov/navigator/nav-upgrade

Claude Code and agent skill by alekspetrov/navigator

Trust tier 2
  • community
Source check pending

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-upgrade

SKILL.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:

  1. Version Detection: Check current Navigator version vs latest
  2. Plugin Update: Execute /plugin update navigator
  3. Verification: Confirm update succeeded
  4. CLAUDE.md Update: Update project configuration (via nav-sync-claude)
  5. Hooks Setup: Install/update token monitoring hooks in project
  6. 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:

bash
# Current installed version
grep '"version"' .claude-plugin/plugin.json
# Get all releases (including pre-releases)
curl -s https://api.github.com/repos/qf-studio/navigator/releases
# Parse:
# - Latest stable (prerelease: false)
# - Latest pre-release (prerelease: true)
# - Compare with current version

Output scenarios:

Scenario 1: Stable update available

json
{
"current_version": "4.0.0",
"latest_stable": "4.2.0",
"latest_prerelease": null,
"recommendation": "update_to_stable"
}

Scenario 2: Pre-release available (user on stable)

json
{
"current_version": "4.0.0",
"latest_stable": "4.0.0",
"latest_prerelease": "4.3.0",
"recommendation": "offer_prerelease_option"
}

Present choice:

✅ You're on the latest stable version (v4.0.0)
⚡ Experimental version available: v4.3.0
New in v4.3.0 (Experimental):
• Knowledge graph with experiential memories
• PM integration with ticket closing
Options:
[1] Stay on stable v4.0.0 (recommended)
[2] Try experimental v4.3.0 (early adopter)
Your choice [1-2]:

Scenario 3: Already on latest (stable or pre-release)

✅ You're on v4.3.0 (latest experimental)
Latest stable: v4.0.0
Status: You're ahead of stable (testing experimental features)
New features in your version:
- Knowledge graph with experiential memories

Skip to Step 5 (Feature Discovery).

Scenario 4: On pre-release, newer stable available

⚠️ You're on v4.3.0 (experimental)
Latest stable: v4.6.0
Recommendation: Update to stable v4.6.0
Experimental features from v4.3.0 are now stable.

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:

markdown
✅ You're on latest stable version (v4.0.0)
⚡ Experimental version available: v4.3.0
New in v4.3.0 (Experimental):
• Knowledge graph with experiential memories
• PM integration with ticket closing
**Question**: Which version would you like?
**Options**:
[1] **Stay on stable v4.0.0** (recommended)
-Production-ready
-No experimental features
-Most reliable
[2] **Try experimental v4.3.0** (early adopter)
-Latest features
-Help test new functionality
Your choice?

If user chooses [1] (Stay stable):

✓ Staying on v4.0.0 (latest stable)
No action needed. Run nav-upgrade again when you're ready to try experimental features.

If user chooses [2] (Try experimental):

bash
# Uninstall current version
/plugin uninstall navigator
# Add marketplace (if not already added)
/plugin marketplace add qf-studio/navigator
# Install specific pre-release version
# Note: /plugin update only fetches stable, must install specific version
git clone https://github.com/qf-studio/navigator.git /tmp/navigator-v4.3.0
cd /tmp/navigator-v4.3.0
git checkout v4.3.0
# Install from local checkout
/plugin install /tmp/navigator-v4.3.0

Then verify installation:

bash
/plugin list | grep navigator
# Should show: navigator (v4.3.0)
Scenario 1: Stable Update Available

Execute: /plugin update navigator

Monitor output:

Updating navigator...
✅ Navigator updated to v4.2.0

If update fails:

❌ Update failed: [error message]
Troubleshooting:
1. Restart Claude Code
2. Try: /plugin uninstall navigator && /plugin install navigator
3. Check internet connection
4. Report issue: https://github.com/qf-studio/navigator/issues

Automatic retry (once): If update fails, try uninstall/reinstall automatically:

bash
/plugin uninstall navigator
/plugin marketplace add qf-studio/navigator
/plugin install navigator

Step 3: Verification

Execute: plugin_verifier.py

Verify:

  1. Plugin version matches latest
  2. New skills registered in plugin.json
  3. Skills are invokable

Test new skills (v3.3.0 example):

bash
# Test that visual-regression skill exists
ls ~/.config/claude/plugins/navigator/skills/visual-regression/SKILL.md 2>/dev/null || echo "Skill not found"

Output:

✅ Update Verification
Version: v3.3.0 ✅
New Skills Registered: visual-regression ✅
Skills Invokable: ✅
Update successful!

If verification fails:

⚠️ Update completed but verification failed
Issue: visual-regression skill not found
Fix: Restart Claude Code to reload skills
After restarting, verify:
"Set up visual regression for Button"

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:

⚠️ RESTART REQUIRED
Plugin updated successfully to vX.Y.Z.
Claude Code caches skill paths at session start.
To use new/updated skills:
1. Close Claude Code
2. Reopen Claude Code
3. Run "nav start" to verify new version
Without restart:
- Old skill versions continue running
- New skills won't be available
- May see "skill not found" errors

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

🔄 Syncing project CLAUDE.md with updated plugin...
✓ Using template from GitHub (v4.3.0)
✓ Extracted customizations
✓ Generated updated CLAUDE.md

What happens automatically:

  1. Detects new plugin version (e.g., v4.3.0)
  2. Fetches matching template from GitHub
  3. Preserves project customizations
  4. Updates CLAUDE.md in current project
  5. 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:

Review changes and commit:
git add CLAUDE.md
git commit -m "chore: update CLAUDE.md to Navigator v4.3.0"

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:

bash
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"
python3 "$PLUGIN_DIR/skills/nav-upgrade/functions/migrate_hooks_out_of_settings.py" \
.claude/settings.json
# Output:
# ✓ Backup written → .claude/settings.json.pre-migrate.<timestamp>
# ✓ Removed N Navigator hook entries (commands path matched)
# ✓ Preserved K unrelated user hooks

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).

⚠️ RESTART REQUIRED to activate hooks from the plugin manifest.
Claude Code caches plugin hook definitions at session start.

Step 6: Post-Upgrade Setup Check

Check if new features require setup:

bash
# Check for skills with setup requirements
if [ -f "$NAVIGATOR_PATH/skills/product-design/setup.sh" ]; then
# Check if venv exists
if [ ! -d "$NAVIGATOR_PATH/skills/product-design/venv" ]; then
echo "⚠️ product-design skill requires setup"
NEEDS_SETUP=true
fi
fi

If setup needed, show instructions:

markdown
⚠️ New Feature Requires Setup
The product-design skill (v3.4.0+) requires Python dependencies:
**One-time setup** (30 seconds):

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

**What this installs**:
- Python MCP SDK for direct Figma connection
- 95% orchestration reduction
- 92% token savings
**After setup, use**:
"Review this Figma design: [URL]"

Record setup needed in TodoWrite for tracking.


Step 7: Feature Discovery

Show new features available in updated version.

For v3.3.0 update:

`markdown
🎉 Navigator v3.3.0 Update Complete!
## New Features Available
### visual-regression Skill (NEW)
Set up Storybook + Chromatic in 5 minutes instead of 2-3 hours.
**Usage**:

"Set up visual regression for ProfileCard" "Add Chromatic to Button component" "Configure visual tests for Input, Card, Modal"

**What it does**:
✅ Generates Storybook stories with all variants
✅ Configures Chromatic/Percy/BackstopJS
✅ Creates CI workflows (GitHub Actions, GitLab CI)
✅ Adds accessibility tests
**Complete Design Pipeline** (v3.2 + v3.3):
1. "Review this design from Figma" (v3.2)
2. Implement components
3. "Set up visual regression" (v3.3 NEW)
4. Automated visual testing in CI
### Updated Skills Count
- **17 total skills** (was 16)
- 10 core Navigator skills
- 7 development skills

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

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
vskill VERIFIED badge
[![vskill VERIFIED](https://verified-skill.com/api/v1/skills/alekspetrov/navigator/nav-upgrade/badge)](https://verified-skill.com/skills/alekspetrov/navigator/nav-upgrade)

Something wrong with this skill or its page? Tell us.