metame-release

Name: metame-release
Availability: InStock
Author: yaron9

Coordinate version bumps, pre-publish audits, and OTP-based publishing for MetaMe npm releases.

18|3|Updated Jan 24, 2026

Search Tags:#workflow #npm #audit #release #version-bump #otp-publish

Ready to run

npx skills add https://github.com/Yaron9/MetaMe --skill metame-release

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: metame-release
Source: https://github.com/Yaron9/MetaMe/tree/main/.claude/skills/metame-release
Command: npx skills add https://github.com/Yaron9/MetaMe --skill metame-release

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

MetaMe npm release workflow enforces a disciplined release process by coordinating version bumps, pre-publish audits, and OTP-based publishing to prevent accidental releases and ensure code context is preserved.

Core Features & Use Cases

Pre-release checks: verify a clean working tree, run linting, and validate deployment integrity before publishing.
Version management: bump versions consistently and commit changes, ensuring traceability in the release history.
Secure publishing: publish with OTP verification to enforce dual-factor authentication for releases.

Quick Start

Initiate a release by bumping the version, auditing changes, and publishing MetaMe with OTP verification.

Frequently Asked Questions about metame-release

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

FAQPage Schema

How do I automate npm release workflows with version bumps and audits?▼

Automate npm release workflows by coordinating version bumps, pre-publish audits, and OTP-based publishing. The process enforces a checklist verifying uncommitted changes, ESLint passes, and deployment integrity before using npm version and npm publish with OTP to guarantee traceable releases.

What pre-publish audits are required before an npm publish?▼

Pre-publish audits require verifying a clean working tree with no uncommitted changes, running ESLint to ensure code quality, validating deployment integrity, and checking plugin script synchronization before executing the npm publish command.

How does OTP-based npm publishing secure package releases?▼

OTP-based npm publishing secures releases by enforcing dual-factor authentication during the npm publish command. This prevents accidental or unauthorized package distribution by requiring a one-time password to complete the publishing process.

Can I release an npm package hotfix with uncommitted changes in the working tree?▼

No, releasing an npm package hotfix requires a clean working tree. The release workflow enforces a checklist that verifies uncommitted changes are resolved, ensuring code context is captured and releases remain traceable before version bumping.

What is the best way to ensure deployment integrity when bumping npm package versions?▼

The best way to ensure deployment integrity when bumping npm package versions is applying a disciplined release workflow that runs pre-release checks, commits version changes for traceability, and validates deployment integrity before secure OTP publishing.