openclaw-release-maintainer

Automate Argentum release workflows from version tagging to publish validation.

2|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/AG064/argentum --skill openclaw-release-maintainer-ag064
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openclaw-release-maintainer
Source: https://github.com/AG064/argentum/tree/main/.agents/skills/argentum-release-maintainer
Command: npx skills add https://github.com/AG064/argentum --skill openclaw-release-maintainer-ag064

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintainer workflow for Argentum releases, prereleases, changelog release notes, and publish validation. Use when Codex needs to prepare or verify stable or beta release steps, align version naming, assemble release notes, check release auth requirements, or validate publish-time commands and artifacts.

Core Features & Use Cases

  • Standardized release choreography from tagging to publish validation across npm and macOS ecosystems.
  • Guardrails for version naming, release notes assembly, and credential checks.
  • Reproducible hands-off workflows for CI/CD integration.

Quick Start

Follow a reproducible release workflow from versioning to publishing checks.

Frequently Asked Questions about openclaw-release-maintainer

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

FAQPage Schema
How do I automate npm release workflows with version tagging and validation?

Automated npm release workflows handle version tagging, changelog generation, and publish validation by applying guardrails to version updates and running preflight checks before publishing artifacts to ensure compliant, auditable releases.

What's the best way to generate changelog release notes for beta and stable versions?

Generating changelog release notes for beta and stable versions is standardized through reproducible workflows that align version naming, assemble release notes automatically, and enforce guardrails on version updates before publish validation.

Does this release workflow support both npm and macOS publish paths?

Yes, the release workflow supports both npm and macOS publish paths by validating publish-time commands and artifacts across both ecosystems, implementing required preflight checks and credential management for compliant, auditable releases.

How do preflight checks and credential management work for release publishing?

Preflight checks and credential management enforce guardrails on version updates and release auth requirements before publish validation, ensuring required checks pass and credentials are managed for compliant, reproducible release workflows.

Can I integrate this release choreography into CI/CD pipelines for hands-off automation?

Yes, the release choreography integrates into CI/CD pipelines by providing reproducible hands-off workflows that standardize the path from version tagging to publish validation, ensuring auditable releases across npm and macOS environments.