devkit-release-maintainer

Name: devkit-release-maintainer
Availability: InStock
Author: xpotato1024

Validate devkit release metadata across tags, installers, and version outputs.

1|Updated Mar 30, 2026

Search Tags:#workflow #versioning #validation #audit #packaging #release #devkit

Ready to run

npx skills add https://github.com/Xpotato1024/xpotato-devkit --skill devkit-release-maintainer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: devkit-release-maintainer
Source: https://github.com/Xpotato1024/xpotato-devkit/tree/main/SKILLs/devkit-release-maintainer
Command: npx skills add https://github.com/Xpotato1024/xpotato-devkit --skill devkit-release-maintainer

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Ensures release metadata, tags, installer packaging, and user-visible version outputs are consistent and auditable across the devkit project.

Core Features & Use Cases

Validate release-facing metadata in README, docs/release, and manifests.
Verify local and CI build behavior for release-tag scenarios.
Provide an auditable, repeatable release-check workflow by integrating the bundled script and references.

Quick Start

Begin by auditing release metadata and version alignment using the built-in checker and scripts.

Frequently Asked Questions about devkit-release-maintainer

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

FAQPage Schema

How do I validate devkit release metadata across installer manifests and version outputs?▼

You validate release metadata by running a bundled checker script that verifies version alignment across README, docs/release, and installer manifests, ensuring tags and user-visible version outputs remain consistent and auditable.

What is release metadata alignment and why does it matter for devkit packaging?▼

Release metadata alignment synchronizes version tags across CLI, installer, and manifest code paths to prevent inconsistent user-visible version outputs and packaging errors during tag publication.

How do I prepare a devkit release tag for CI build validation?▼

Prepare a devkit release tag by verifying the checker script and references exist, then validate local and CI build behavior for release-tag scenarios to ensure the workflow injects the correct version into all code paths.

Can I use this release validation workflow without external dependencies?▼

Yes, you can use this release validation workflow without external dependencies, as it relies entirely on bundled scripts and references to provide an auditable, repeatable release-check process for your devkit.

What is the best way to audit release notes and version consistency before publication?▼

The best way to audit release notes and version consistency is to use an integrated checker script that validates release-facing metadata across docs, manifests, and CLI outputs before tag publication and packaging.

Why does my devkit installer manifest show a different version than the CLI output?▼

Your installer manifest and CLI output differ because the release workflow failed to inject the release version consistently across all code paths, an issue resolved by validating release metadata alignment before packaging.