publish-akasha-navigator

Analyze AkashaNavigator release readiness and recommend the next semantic version.

34|Updated Dec 12, 2025
One-click install
npx skills add https://github.com/ColinXHL/akasha-navigator --skill publish-akasha-navigator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: publish-akasha-navigator
Source: https://github.com/ColinXHL/akasha-navigator/tree/main/.agents/skills/publish-akasha-navigator
Command: npx skills add https://github.com/ColinXHL/akasha-navigator --skill publish-akasha-navigator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and assets (resource) components.

What problem does it solve?

This Skill removes the guesswork and risk from releasing AkashaNavigator by helping you decide whether a new version is warranted, what version number to use, and how to publish binaries and update metadata correctly.

Core Features & Use Cases

  • Release Decision Analysis: Reviews project version, latest GitHub Release, commits since the last tag, and working tree state to decide whether a release should happen.
  • Semantic Versioning Guidance: Recommends patch, minor, major, or alpha version bumps based on the actual scope and user impact of changes.
  • End-to-End Publishing: Coordinates branch preparation, tests, GitHub Actions publishing, GitHub Release publication, and updater manifest updates so users can detect the new version.
  • Operational Safety: Preserves unrelated working-tree changes, requires explicit confirmation before publishing, and verifies release artifacts and updater visibility before declaring success.

Quick Start

Use the publish-akasha-navigator skill to assess the current changes, recommend the next version, and wait for my confirmation before publishing the release.

Frequently Asked Questions about publish-akasha-navigator

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

FAQPage Schema
How do I decide the correct semantic version for a new GitHub release?

Semantic versioning decisions require analyzing commit diffs since the latest tag to recommend patch, minor, major, or alpha bumps based on actual change scope and user impact.

What is the safest workflow for publishing binary releases via GitHub Actions?

Safely publishing binary releases involves preparing the branch, running tests, triggering GitHub Actions, publishing the GitHub Release, and synchronizing updater manifests so users detect the update.

Why are users not seeing my latest application update after publishing?

Update-notice troubleshooting often stems from failing to synchronize the updater manifest after publishing the GitHub Release, which prevents users from detecting the newly available version.

Can I preserve unrelated working-tree changes when preparing a release?

Operational safety during release preparation preserves unrelated working-tree changes, while requiring explicit confirmation before executing any publication step to prevent accidental commits.

When should I avoid creating a new release for my repository?

Release readiness analysis prevents creating a new version when there are no significant commits since the last tag, or when working tree validation and release artifact verification fail.