Skip to content

verify-github-npm-release

skill

A release-verification skill for Codex and Claude Code that compares local Git state, GitHub tags and releases, npm versions and dist-tags, CI evidence, advertised commands, and optional catalog records without changing release state.

A release-verification skill for Codex and Claude Code that compares local Git state, GitHub tags and releases, npm versions and dist-tags, CI evidence, advertised commands, and optional catalog records without changing release state.

verify-github-npm-release is a AI-agent skill created to make a real workflow clearer, faster, and easier to trust. It turns a focused product idea into something people can use, evaluate, and understand without needing to inspect the source code.

Why verify-github-npm-release exists

A release can look complete in one system while its tag, package version, CI, install instructions, or catalog entry points elsewhere.

The goal is not simply to add another tool. verify-github-npm-release is designed to reduce the friction around that problem and give people a more dependable way to complete the work.

What it delivers

  • Agents can detect version/tag drift.
  • Distinguish missing artifacts from blocked verification.
  • Report exact failing surfaces.
  • Provide evidence links without claiming an install was executed.

The experience

Performs a read-only audit across GitHub releases, npm packages, tags, CI, and install commands.

The project brings the important parts of the workflow into one coherent experience. Its interface and behavior are shaped around the people using it, while the implementation stays focused on predictable results and honest feedback.

What to know

Every product has boundaries. These are the most important considerations for verify-github-npm-release:

  • Auditing must never mutate or repair release state.
  • Authentication/network errors cannot be interpreted as artifact absence.
  • Mutable aliases such as latest are weaker proof than package@version.

These limitations are presented openly so visitors can understand where the project works well, what it depends on, and what may change in future versions.

Current status

Published npm package v0.1.0. The current release demonstrates the core value of the project and the main end-to-end experience.

My role was agent workflow design and automation engineering, covering agent workflow, validation automation, and packaging. The related case study explains the decisions and delivery process in greater depth for visitors who want the engineering story behind the product.

Project stack

  • Agent Skills
  • JavaScript
  • Node.js
  • npm
  • GitHub Actions
  • CI/CD
  • Git

Need help with this project? Get project support

Working through something similar?

Share your challenge, scope, and timeline to start a focused conversation.

Discuss a project