nav-release

# Navigator Release Skill Validate plugin integrity and release to marketplace with all safety checks. ## Why This Exists After v5.1.0 incident where nav-profile was referenced in plugin.json but never committed, causing install failures. This skill ensures: - All referenced skills exist and are committed - Version consistency across all files - Tag created AFTER all commits - Post-release verification ## When to Invoke **Auto-invoke when**: - User says "release plugin", "publish navigator" - User says "create release", "deploy new version" - User says "release vX.Y.Z" **DO NOT invoke if**: - Just committing changes (no release) - Updating documentation only - Testing locally ## Execution Steps ### Step 1: Pre-Release Validation [CRITICAL] **Run validation script**: ```bash python3 functions/release_validator.py --check-all ``` This validates: 1. All skills in plugin.json exist 2. All skill files are committed (not untracked) 3. Version consistency across files 4. No uncommitted changes in skills/ **If validation fails**: STOP and fix issues before proceeding. ### Step 1.5: Hook Smoke Test [STRONGLY RECOMMENDED for any release touching hooks or plugin.json] **Run hook smoke-test**: ```bash python3 functions/release_validator.py --verify-hooks ``` This executes every plugin manifest hook command via `bash` twice — once with `$CLAUDE_PLUGIN_ROOT` bound to the latest cache version, once with it explicitly unset (`env -u CLAUDE_PLUGIN_ROOT`). It detects the **v6.1...