Release version integrity

Skill chf3198/megingjord-harness/skills/release-version-integrity

Validate and enforce release version integrity across tags, manifests, changelogs, and publish workflows. Use before tagging, publishing, or when release metadata drift is suspected.From its SKILL.md

Install

npx -y skills add chf3198/megingjord-harness --skill release-version-integrity

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.0 KB, 346 tokens by cl100k_base, as published. Nobody here has run it

Release Version Integrity

When to use

Before any release or publish action.
When package.json/manifest version, git tag, and changelog may be inconsistent.
After cherry-picks or hotfixes that bypassed normal release flow.

Procedure

Detect release source-of-truth files (manifest + changelog + workflow triggers).
Compare tag version, manifest version, and changelog head version.
Determine the canonical install channel and whether exact-version install/pinning is supported.
Check publish workflow for explicit version/tag validation gates.
Confirm artifact preflight exists (vsce ls/equivalent package manifest audit).
Require a post-publish availability gate for exact-version installability when platform supports it.
Verify update notifications and release announcements use the same canonical version source as installers.
Propose the smallest change that makes drift structurally unlikely.

Output format

integrity_status: pass|fail
drift_points: exact mismatches found
version_selectability: supported|not-supported|unknown
selectability_status: pass|fail|n/a
required_gates: missing required checks
minimal_fix_plan: ordered steps to remediate
evidence: files and checks reviewed

Standards

Do not claim release readiness without explicit evidence.
Prefer automated versioning flows over manual multi-file updates.
Keep release metadata factual and traceable.
For platforms supporting exact-version install/pinning, do not mark readiness unless exact-version installability is verified post-publish.
Require immutable release artifacts and documented retention/yank policy for versioned channels.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.