nav-release

Validates and automates Navigator plugin releases to the marketplace.

32|3|Updated Jan 21, 2026
One-click install
npx skills add https://github.com/dkyazzentwatwa/SuperNavigator --skill nav-release
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nav-release
Source: https://github.com/dkyazzentwatwa/SuperNavigator/tree/main/skills/os-layer/project-management/nav-release
Command: npx skills add https://github.com/dkyazzentwatwa/SuperNavigator --skill nav-release

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the critical validation and release process for the Navigator plugin, preventing deployment errors and ensuring a stable user experience.

Core Features & Use Cases

  • Pre-Release Validation: Ensures all skills exist, are committed, and versions are consistent across all configuration files.
  • Automated Release Steps: Handles committing changes, pushing to main, creating Git tags, and publishing GitHub releases.
  • Post-Release Verification: Confirms the released tag contains all necessary components and instructs users on how to test.

Quick Start

Use the nav-release skill to release version 5.2.0 of the Navigator plugin.

Frequently Asked Questions about nav-release

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

FAQPage Schema
How do I validate plugin versions before a Git release deployment?

To validate plugin versions before a Git release deployment, check version consistency across plugin.json, marketplace.json, CLAUDE.md, and README.md, and verify all skills exist and are committed.

What is the best way to automate GitHub releases using Git tags?

The best way to automate GitHub releases using Git tags is to enforce pre-release integrity checks, push commits to main, create Git tags, and use the `gh` CLI to publish the release.

Do I need the gh CLI to automate plugin marketplace deployment?

Yes, you need the `gh` CLI installed to automate plugin marketplace deployment, as the release process relies on it to create the GitHub release after Git tagging and pushing.

Why does my deployment validation fail when releasing a plugin?

Deployment validation fails when releasing a plugin if there are missing skills, uncommitted changes, or version mismatches between your plugin.json, marketplace.json, CLAUDE.md, and README.md files.

How does post-release verification work for GitHub plugin deployments?

Post-release verification for GitHub plugin deployments confirms the newly released Git tag contains all necessary components and instructs users on how to test the deployed plugin.