release

Name: release
Availability: InStock
Author: nich

Automate ClawRouter releases with version sync, builds, tests, and GitHub releases.

71|22|Updated Apr 6, 2020

Search Tags:#automation #git #changelog #versioning #release #ci-cd

Ready to run

npx skills add https://github.com/nirholas/agenti --skill release-nirholas

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release
Source: https://github.com/nirholas/agenti/tree/main/packages/protocols/x402-clawrouter/skills/release
Command: npx skills add https://github.com/nirholas/agenti --skill release-nirholas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures every ClawRouter release follows a strict, end-to-end checklist, preventing missed steps and inconsistent releases.

Core Features & Use Cases

Enforces version sync, CHANGELOG updates, and blockrun server constant updates across the repository.
Automates build, test, npm publish, git tagging, and GitHub release steps to produce reliable, auditable releases.
Use Case: When preparing a new ClawRouter release, run this skill to verify all steps are completed in order and generate a GitHub release with accurate notes.

Quick Start

Execute the release skill to run the full release checklist for the next ClawRouter version.

Frequently Asked Questions about release

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

FAQPage Schema

How do I automate git releases with a strict versioning and CHANGELOG checklist?▼

Automating git releases involves enforcing version sync, CHANGELOG updates, build tests, npm publishing, and git tagging in sequence. This release process validates version increments and generates GitHub releases with accurate notes to prevent missed steps.

What is an end-to-end release checklist for CI-CD automation?▼

An end-to-end release checklist for CI-CD automation covers version syncing, CHANGELOG updates, server constant updates, builds, tests, npm publishing, git tagging, and GitHub releases. It ensures every release step is completed in order for reliable, auditable artifacts.

How do I update CHANGELOG and version constants before publishing an npm package?▼

To update CHANGELOG and version constants before publishing an npm package, enforce version sync across the repository and update server constants. The release process validates these increments and updates references before building artifacts and running tests.

Does automated release automation handle git tagging and GitHub release generation?▼

Yes, release automation handles git tagging and GitHub release generation. After building artifacts and running tests, the process ensures release artifacts are published and tagged correctly, automatically generating a GitHub release with accurate notes.

What is the best way to validate version increments during a release?▼

The best way to validate version increments during a release is to enforce a full checklist that syncs versions and updates references across the repository. This ensures consistent releases by verifying increments before building and publishing artifacts.