nav-upgrade_skill

Overview

This skill automates Navigator plugin upgrades end-to-end, from version detection through verification, project sync, and feature validation. It reduces a routine 10–15 minute manual process to around 2 minutes by running targeted tools and handling common failure modes. The skill auto-invokes when you mention upgrading Navigator or requesting new features so updates are seamless and repeatable.

How this skill works

The skill runs a version detector to compare the installed Navigator version with stable and pre-release releases. Based on the result it either runs a standard plugin update or performs an uninstall/install for specific pre-release versions, then verifies files, skills, and invocations. After a successful update it syncs the project configuration file, installs token-monitoring hooks, checks for any post-update setup tasks, and surfaces new features and required actions.

When to use it

• You want to upgrade Navigator to the latest stable or try an experimental release
• You noticed new Navigator features and want them available in your project
• You want automatic verification and project config sync after a plugin update
• You need token usage monitoring and hook setup installed automatically
• You prefer an automated safe retry if the first update attempt fails

Best practices

• Run the skill from the project root so CLAUDE.md and .claude hooks are detected and updated
• Review the presented choice when a pre-release is available; experimental builds may be unstable
• Restart the Claude Code application after updates to load new skills from the updated plugin
• Review the generated diff for CLAUDE.md before committing to preserve customizations
• Keep a backup of .claude/settings.json before the skill writes hook configuration

Example use cases

• Upgrade Navigator from v3.2.0 to v3.3.0 and automatically add the visual-regression skill to the project
• Switch to a specific pre-release when you want to test a new multi-agent workflow
• Automatically install token monitoring hooks to avoid context budget crashes in long sessions
• Run a verification pass that checks new skills are present and invokable, then prompt for restart
• Apply template updates to CLAUDE.md and present a diff so you can commit changes safely