nav-release_skill

This skill validates plugin integrity and automates release steps to ensure safe, consistent Navigator marketplace deployments.
  • Python

142

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill alekspetrov/navigator --skill nav-release

  • SKILL.md5.2 KB

Overview

This skill validates Navigator plugin integrity and automates releasing the plugin to the marketplace. It runs safety checks, enforces version consistency, and performs the git and GitHub release steps only after validation passes. It is triggered by release commands like "release plugin" or "publish navigator".

How this skill works

The skill runs a pre-release validator that checks referenced skills exist, are committed, and that versions match across plugin.json, marketplace.json, and docs. After validation, it prompts for a release confirmation, performs commits and pushes, creates a git tag, and creates a GitHub release. Finally it verifies the tag contents and suggests local cache clearing and installation tests.

When to use it

  • When you want to publish a new Navigator version (e.g., "release vX.Y.Z").
  • When you need to ensure all referenced skills are present and committed before release.
  • When you must enforce version consistency across all plugin files.
  • When you are ready to create a git tag and GitHub release after final checks.
  • Do not invoke for local testing, documentation-only edits, or ordinary commits.

Best practices

  • Run python3 functions/release_validator.py --check-all and fix any failures before proceeding.
  • Only create the git tag after all commits have been pushed to origin/main.
  • Confirm the release version interactively before tagging and publishing.
  • Keep release notes in RELEASE-NOTES-vX.Y.Z.md and attach them to the GitHub release.
  • After release, run the post-release verifier and clear local plugin cache before testing.

Example use cases

  • User says "release plugin" and the skill validates, tags v2.4.0, and creates the GitHub release.
  • Run validation alone with "Validate plugin for release" to check missing or uncommitted skills.
  • Recover from a failed release by fixing missing skills or version mismatches and re-running validation.
  • Publish a hotfix by confirming the incremented version and letting the skill push, tag, and release.
  • Verify a published tag contains all skills using python3 functions/release_validator.py --verify-tag vX.Y.Z

FAQ

The release stops. Fix missing skills, commit untracked changes, or correct version mismatches, then re-run validation.

When is the git tag created?

The git tag is created only after commits are pushed to origin/main and after you confirm the release version.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational
nav-release skill by alekspetrov/navigator | VeilStrat