release

Run type checks, linting, formatting, tests, and builds for Terrae component releases.

243|5|Updated Jan 16, 2026
One-click install
npx skills add https://github.com/alamenai/terrae --skill release-alamenai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/alamenai/terrae/tree/main/.claude/skills/release
Command: npx skills add https://github.com/alamenai/terrae --skill release-alamenai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prepare a Terrae component for release by running all checks and builds to ensure quality and readiness for publication.

Core Features & Use Cases

  • Pre-release checklist: type check, lint, format check, tests
  • Build and publish: registry build to ./public/maps and production build
  • Verification and safeguards: report results, avoid automatic pushes or version changes

Quick Start

Use the release skill to validate, build, and prepare the component for registry deployment.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate TypeScript compilation and npm checks before a component release?

Automating TypeScript compilation and npm checks before a component release involves running type checking, linting, formatting, and tests to ensure code quality. This process validates the build readiness without automatically pushing changes or altering versions.

What is the best way to prepare a Terrae component for npm registry publication?

Preparing a Terrae component for npm registry publication requires executing a pre-release workflow that builds the registry output to ./public/maps and runs a production build. This verifies all quality checks pass before deployment.

Can I run lint and format checks without triggering an automatic version bump during the release process?

Yes, you can run lint and format checks without triggering an automatic version bump. The release process provides final verification and reports results while specifically avoiding automatic pushes or version changes to your repository.

What steps are needed to validate a component build in a pre-release CI/CD environment?

Validating a component build in a pre-release CI/CD environment requires passing TypeScript compilation, linting, formatting, and testing scripts. After these checks, the workflow executes the registry and production builds to confirm publication readiness.

Does this release workflow automatically push code changes or publish builds to the registry?

No, this release workflow does not automatically push code changes or publish builds. It is designed for verification and safeguards, running the necessary checks and builds to report readiness while explicitly avoiding automated pushes or version changes.