cli-release

Automate @einja/cli package builds, tests, versioning, tagging, changelog notes, and GitHub publishing with enforced checks using pnpm, npm, and gh tools.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the release workflow for the @einja/cli package, reducing manual steps and risk of human error during publishing.

Core Features & Use Cases

  • Build, test, and publish the CLI package across versions
  • Tag releases automatically and push to main branches
  • Validate workspace state (no uncommitted changes) before releasing

Quick Start

Run the release workflow from the repository root after ensuring you are on the main branch with a clean working tree.

Frequently Asked Questions about cli-release

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

FAQPage Schema
How do I automate CLI package publishing with build, test, and git tag checks?

Automating CLI package publishing involves running a release workflow that validates branch state, executes build and test commands, handles versioning, and publishes to GitHub with proper tagging and changelog notes. This ensures uncommitted changes are blocked before release.

What checks are enforced before publishing an npm CLI package to GitHub?

Before publishing an npm CLI package, the release workflow enforces checks on the current branch, detects uncommitted changes, validates version selection, and monitors GitHub Actions. This prevents accidental releases from unclean or incorrect workspace states.

Can I use pnpm and gh tools to release a CLI package across mainline flows?

Yes, the release workflow supports using pnpm, npm, and gh tools to build, test, and publish CLI packages across mainline flows. It manages versioning and pushes tags to main branches automatically.

How do I tag releases and generate changelog notes for a CLI package?

Tagging releases and generating changelog notes is handled automatically by the release workflow during the publish step. It creates git tags and pushes them to the main branch alongside the published package.

Why does my CLI release workflow fail when there are uncommitted changes?

The CLI release workflow fails on uncommitted changes because it enforces workspace state validation to reduce human error. You must be on the main branch with a clean working tree before initiating the release process.