create-einja-app-release

Automate build, test, and publish of create-einja-app to npm.

1|Updated Jun 15, 2025
One-click install
npx skills add https://github.com/einja-inc/einja-management-template --skill create-einja-app-release
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-einja-app-release
Source: https://github.com/einja-inc/einja-management-template/tree/main/.claude/skills/create-einja-app-release
Command: npx skills add https://github.com/einja-inc/einja-management-template --skill create-einja-app-release

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates end-to-end release of the create-einja-app package by building, testing, and publishing to npm.

Core Features & Use Cases

  • Build, test, typecheck, and lint the create-einja-app package.
  • Manage versioning and git tagging with a standardized tag format (create-einja-app-v{version}) and publish to npm.
  • Monitor and synchronize with GitHub Actions CI to ensure releases finish successfully and surface failures for quick remediation.

Quick Start

Initiate the release flow on the main branch and follow the on-screen prompts to build, test, version, tag, push, and monitor the release in GitHub Actions.

Frequently Asked Questions about create-einja-app-release

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

FAQPage Schema
How do I automate npm package releases in a monorepo with git tagging and CI/CD monitoring?

Automate npm package releases in a monorepo by running build, test, lint, and typecheck pre-release checks, pushing standardized git tags, publishing to npm, and monitoring GitHub Actions CI for build status.

What pre-release checks are required before publishing an npm package?

Required pre-release checks before publishing an npm package include running build, test, typecheck, and lint validations to ensure all code changes are properly committed and the package is stable.

Does this release workflow support standardized git tagging for monorepo packages?

Yes, this release workflow supports standardized git tagging for monorepo packages by automatically generating and pushing tags using a standardized format like package-name-v{version} to the origin repository.

How can I monitor GitHub Actions CI status during an npm publish workflow?

Monitor GitHub Actions CI status during an npm publish workflow by synchronizing with the CI pipeline to ensure releases finish successfully and surfacing any failures for quick remediation.

What is the best way to handle version selection when publishing npm packages automatically?

Handle version selection when publishing npm packages automatically by initiating the release flow on the main branch and following on-screen prompts to select, tag, and push the new version.

Why do my npm releases fail in GitHub Actions after pushing git tags?

npm releases fail in GitHub Actions after pushing git tags when pre-release checks like build, test, typecheck, or lint are incomplete or uncommitted changes exist, which the automated workflow surfaces for quick remediation.