skills.rest
slopus
slopusOFFICIAL
Explore all skills by this author →
WebsiteGitHub

release

Automate versioning, builds, tests, and publishing for Happy components.

23.2k|2.0k|Updated Jul 18, 2025
Search Tags:#version control#CI/CD#release automation#npm publishing#mobile builds
One-click install
npx skills add https://github.com/slopus/happy --skill release-slopus
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/slopus/happy/tree/main/.agents/skills/release
Command: npx skills add https://github.com/slopus/happy --skill release-slopus

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires npm, eas, git, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates and guides the release process for Happy's CLI, mobile, web, and server components, replacing the old interactive release-it flow with a Claude Code-native experience.

Core Features & Use Cases

  • Release Automation: Automates version bumping, building, testing, publishing, and deploying for CLI, mobile, web, and server components.
  • Version Control: Handles cli-X.Y.Z and native-<runtime-version> tagging systems, ensuring correct versioning.
  • Build and Test: Executes builds and unit tests for CLI components, skipping integration tests for efficiency.
  • Publishing: Manages npm publishing with proper tag management and channel selection.
  • Documentation: Provides clear instructions for Git tagging and committing, as well as GitHub release creation for latest releases.

Quick Start

To release the Happy CLI, use the command: happy release cli

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate npm publishing and version control for a CLI project?▼

Use the `happy release cli` command to automate npm publishing and version control. It handles version bumping, executes builds, runs unit tests, and publishes to npm while managing tags like `cli-X.Y.Z` automatically.

How does EAS build integration work for mobile release automation?▼

Mobile release automation uses EAS to manage builds and native versioning via `native-<runtime-version>` tags. It coordinates the build pipeline for mobile components, ensuring correct runtime versions are tagged and deployed.

Can I use this release automation workflow for Docker and Kubernetes deployments?▼

Yes, this release automation supports Docker and Kubernetes deployments. It handles CI configurations for both Docker and K8s, managing server component builds and deploying them directly through the automated release pipeline.

What is the best way to skip integration tests during a CLI release build?▼

Use the automated release process to skip integration tests during a CLI release. It executes builds and unit tests for CLI components while explicitly skipping integration tests to optimize release speed and efficiency.

Do I need Git and npm access to automate GitHub release creation?▼

Yes, Git and npm access are required for GitHub release creation. The workflow uses Git for tagging and committing instructions, and npm for publishing, to generate GitHub releases specifically for `latest` distribution tags.

Related Skills

Explore More Software Engineering Skills→
phnx-labsphnx-labs
15

release

Automate versioning, testing, changelog generation, and registry publishing for software releases.

Official
Advanced
klaudworksklaudworks
181

npm-publisher

Automate npm package releases with version bumps, Git tags, and CI/CD publishing.

Community
Intermediate
JayFareiJayFarei
92

release-pack

Orchestrate full software package releases with version bumps, documentation checks, and automated publishing.

Community
Advanced
sgcarstrendssgcarstrends
21

release-management

Automate software release workflows with semantic-release and conventional commits.

Official
Advanced