nav-upgrade

Automates Navigator plugin updates with version detection, verification, and CLAUDE.md synchronization.

232|12|Updated Oct 10, 2025
One-click install
npx skills add https://github.com/qf-studio/navigator --skill nav-upgrade-qf-studio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nav-upgrade
Source: https://github.com/qf-studio/navigator/tree/main/skills/nav-upgrade
Command: npx skills add https://github.com/qf-studio/navigator --skill nav-upgrade-qf-studio

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Manually updating the Navigator Claude Code plugin involves checking versions, running update commands, verifying skill registration, migrating legacy hooks, and syncing project configuration—a 10-15 minute process prone to missed steps and stale cached skills. ## Core Features & Use Cases - Version Detection: Compares the installed plugin version against GitHub releases, distinguishing stable from pre-release versions and skipping malformed releases whose plugin.json version mismatches the tag. - Update with Retry and Verification: Executes the plugin update, falls back to uninstall/reinstall on failure, and verifies that new skills exist on disk and are registered in plugin.json. - Legacy Hook Migration: Removes outdated Navigator hook entries from .claude/settings.json with timestamped backups, conservative matching, and idempotent re-runs. - Use Case: A user says "Update Navigator" and the skill detects v6.10.0 → v6.15.6, updates the plugin, migrates stale hooks, syncs CLAUDE.md via nav-sync-claude, and reports new features—prompting a restart so cached skill paths reload. ## Quick Start Ask the assistant to update Navigator to the latest version and verify the installation.

Frequently Asked Questions about nav-upgrade

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I update the Navigator Claude Code plugin?

Say "Update Navigator" to trigger the skill, which detects your current version, runs the plugin update, verifies new skills are registered, and syncs your project CLAUDE.md. A Claude Code restart is required afterward because skill paths are cached at session start.

How do I install a pre-release version of a Claude Code plugin?

The skill detects pre-releases from the GitHub releases API and offers a choice between stable and experimental versions. Choosing experimental clones the tagged release from GitHub and installs it locally, since the standard update command only fetches stable releases.

Why are new skills not found after a plugin update?

Claude Code caches skill paths at session start, so updated files are not picked up by the active session. Restart Claude Code, then verify with the plugin list command and test invoking the new skill.

How do I remove legacy Navigator hooks from .claude/settings.json?

Run the migrate_hooks_out_of_settings.py script against your settings file. It removes only entries whose command references hooks/ plus a known Navigator hook name, writes a timestamped backup first, and is idempotent on re-runs.

What happens if the plugin update fails?

The updater automatically retries once by uninstalling and reinstalling the plugin from the marketplace. If both attempts fail, it reports troubleshooting steps including checking the network connection and restarting Claude Code.