release-create

Validate version consistency and create annotated git tags for releases.

2|Updated Feb 17, 2026
One-click install
npx skills add https://github.com/clawperator/clawperator --skill release-create
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-create
Source: https://github.com/clawperator/clawperator/tree/main/.agents/skills/release-create
Command: npx skills add https://github.com/clawperator/clawperator --skill release-create

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, npm, node, gh, python3, and includes scripts (resource) components.

What problem does it solve?

This skill automates the end-to-end release process by validating version consistency across repository files, creating annotated git tags, and orchestrating subsequent release workflows, reducing manual steps and human error.

Core Features & Use Cases

  • Version verification: Ensures apps/node/package.json and apps/node/package-lock.json reflect the target version.
  • Changelog validation: Requires exactly one matching release entry for the target version in CHANGELOG.md.
  • Workflow orchestration: Triggers and monitors CI workflows (npm publish and APK release) and performs a follow-up published-version update when ready.
  • Safety and guardrails: Enforces tags, prevents overwrites, and validates preconditions before tagging.

Quick Start

Run the script with a version and optional sha to create and publish a release.

Frequently Asked Questions about release-create

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

FAQPage Schema
How do I automate git tag creation and npm publish in a CI workflow?

Automate git tag creation and npm publish by validating version consistency across package files and CHANGELOG.md, creating an annotated tag, and triggering CI pipelines for publishing. This coordinates end-to-end release workflows while reducing manual errors.

How does version validation work before creating a git release tag?

Version validation checks that apps/node/package.json and apps/node/package-lock.json match the target version, requires exactly one corresponding entry in CHANGELOG.md, and verifies no existing git tag conflicts before proceeding with the annotated tag creation.

Do I need GitHub CLI and npm installed to automate release tagging?

Yes, automating release tagging requires git, npm, node, gh, and python3 installed. These dependencies enable version verification, annotated tag creation, GitHub release validation, and CI/CD workflow orchestration for npm publishing.

What happens if a git tag or GitHub release already exists for the target version?

The release workflow enforces safety guardrails that prevent overwrites and validate preconditions before tagging. If an existing tag or release is detected, the process halts to avoid duplicate or conflicting release entries.

Can I trigger an APK release and npm publish together from a single git tag?

Yes, the workflow orchestration triggers and monitors multiple CI workflows, including npm publish and APK release, from a single annotated tag. It performs a follow-up published-version update once the pipelines complete successfully.