Cline CLI Release Publisher
cline/cline
Walks through releasing the Cline CLI package to npm: release notes, version bump, matching git tag, and either the GitHub workflow or a local publish.
Guides the UUI package release process including stable and beta releases, changelog updates, and handling failed releases.
Install Uui Release Workflow
$ npx skills add epam/UUI --skill uui-release-workflow -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install epam/UUI uui-release-workflow --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/epam/UUI.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.cursor/skills/release-workflow .claude/skills/uui-release-workflow && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "uui-release-workflow" agent skill from https://github.com/epam/UUI/tree/develop/.cursor/skills/release-workflow into .claude/skills/uui-release-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "uui-release-workflow", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/epam/UUI/tree/develop/.cursor/skills/release-workflowType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add epam/UUI --skill uui-release-workflow -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install epam/UUI uui-release-workflow --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/epam/UUI.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.cursor/skills/release-workflow .agents/skills/uui-release-workflow && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "uui-release-workflow" agent skill from https://github.com/epam/UUI/tree/develop/.cursor/skills/release-workflow into .agents/skills/uui-release-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "uui-release-workflow", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add epam/UUI --skill uui-release-workflow -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install epam/UUI uui-release-workflow --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/epam/UUI.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.cursor/skills/release-workflow .cursor/skills/uui-release-workflow && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "uui-release-workflow" agent skill from https://github.com/epam/UUI/tree/develop/.cursor/skills/release-workflow into .cursor/skills/uui-release-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "uui-release-workflow", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/epam/UUI.git --path .cursor/skills/release-workflow--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add epam/UUI --skill uui-release-workflow -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install epam/UUI uui-release-workflow --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/epam/UUI.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.cursor/skills/release-workflow .gemini/skills/uui-release-workflow && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "uui-release-workflow" agent skill from https://github.com/epam/UUI/tree/develop/.cursor/skills/release-workflow into .gemini/skills/uui-release-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "uui-release-workflow", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install epam/UUI uui-release-workflowInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add epam/UUI --skill uui-release-workflow -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/epam/UUI.git skills-src && mkdir -p .github/skills && cp -r skills-src/.cursor/skills/release-workflow .github/skills/uui-release-workflow && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "uui-release-workflow" agent skill from https://github.com/epam/UUI/tree/develop/.cursor/skills/release-workflow into .github/skills/uui-release-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "uui-release-workflow", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add epam/UUI --skill uui-release-workflow -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install epam/UUI uui-release-workflow --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/epam/UUI.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.cursor/skills/release-workflow .opencode/skills/uui-release-workflow && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "uui-release-workflow" agent skill from https://github.com/epam/UUI/tree/develop/.cursor/skills/release-workflow into .opencode/skills/uui-release-workflow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "uui-release-workflow", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
uui-release-workflow- GitHub stars
- 248
- Token cost
- ~867 tokens
- SKILL.md length
- 437 words
- Files
- 1
- Skills in repo
- 10
- Repo updated
- First seen
- Licence
- MIT
At a glance
Guides the UUI package release process including stable and beta releases, changelog updates, and handling failed releases.
- Works in 2 steps: Version bump (local) — yarn release runs… → Publish (GitHub Actions) — the…
- Releasing UUI packages
- SKILL.md covers Important, How publishing works, Prerequisites and Stable Release, plus 4 more sections
- Calls yarn, git and lerna
What it does
Uui Release Workflow is an agent skill from epam/UUI. Guides the UUI package release process including stable and beta releases, changelog updates, and handling failed releases. Use when releasing UUI packages, updating changelog, or troubleshooting release issues. For maintainers only.
Its SKILL.md is about 870 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Deployment and Changelog and release notes. It works with npm and GitHub Actions. The repository describes itself as: React-based components and accelerators library built by EPAM Systems. The licence is MIT.
When your agent uses it
- Releasing UUI packages
- Updating changelog
- Troubleshooting release issues
Example prompts
- “Use the uui-release-workflow skill to guide the UUI package release process including stable and beta releases, changelog updates, and handling…”
- “/uui-release-workflow”
Workflow steps
2 steps, taken from the first numbered list in SKILL.md.
- Version bump (local) — yarn release runs lerna version --force-publish interactively. Lerna creates a version commit, tag, and pushes both…
- Publish (GitHub Actions) — the maintainer manually triggers the Release workflow in GitHub, selects the tag and dist-tag, approves the…
What it can do on your machine
Read from SKILL.md and the folder at commit fd11393. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
yarngitlerna
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use yarn and git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Uui Release Workflow loads about 867 tokens when it runs. Until then it costs about 64 tokens; SKILL.md has 437 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from epam/UUI at commit fd11393, republished under its MIT licence (© epam). 437 words, ~867 tokens.
Download SKILL.mdSave it as
.claude/skills/uui-release-workflow/SKILL.md (or your agent's skills folder).- name
- uui-release-workflow
- description
- Guides the UUI package release process including stable and beta releases, changelog updates, and handling failed releases. Use when releasing UUI packages, updating changelog, or troubleshooting release issues. For maintainers only.
UUI Release Workflow
Important
Always ask for explicit user permission before triggering a release. Publishing packages to npm cannot be undone. Never initiate the publish workflow without confirming the user intends to do so.
Before asking for permission, provide a pre-publish summary:
- Version: The version that will be published (from
changelog.mdtop section or Lerna) - Packages: Which packages will be published (from
package.jsonworkspaces) - Summary: Brief highlights of changes from the current
changelog.mdentry
How publishing works
Publishing is done via GitHub Actions using npm Trusted Publishers (OIDC). No npm token or OTP is required.
The release process has two parts:
- Version bump (local) —
yarn releaserunslerna version --force-publishinteractively. Lerna creates a version commit, tag, and pushes both to the release branch. - Publish (GitHub Actions) — the maintainer manually triggers the
Releaseworkflow in GitHub, selects the tag and dist-tag, approves thenpm-publishenvironment gate, and CI publishes all 13 packages.
Prerequisites
- Release branch created from
develop(e.g.release/vX.Y.Z) changelog.mdupdated with all released changes- Builds verified:
yarn build
Stable Release
- On the release branch, run:
yarn release - Lerna prompts for version type — choose patch / minor / major
- Lerna commits the version bump, creates tag
vX.Y.Z, pushes to the release branch - Go to GitHub → Actions → Release → Run workflow
tag: the tag from step 3 (e.g.v6.5.3)dist_tag:latestdry_run:false
- Approve the deployment in the
npm-publishenvironment - After successful publish: post changelog to GitHub Releases and UUI Teams channel
- Open PR from release branch into
main - Sync
mainback intodevelop(see dev-docs/release-workflow.md for steps)
Show full SKILL.md (172 more words)Show less
Beta Release
Same steps, with:
- In step 2, enter a prerelease version when prompted (e.g.
6.5.3-beta.0) - In step 4, set
dist_tagtobeta
Dry Run (testing)
Trigger the workflow with dry_run: true (default) and an existing tag to validate the build and publish steps without actually uploading to npm.
Handling Failed Releases
If the release fails after Lerna already created the version commit and tag:
- Revert the version bump commit
- Delete local tag:
git tag -d <tag_name> - Delete remote tag:
git push --delete origin <tag_name> - Fix the issue and run
yarn releaseagain
Release Checklist
- Release branch created from
develop - All changes merged into the release branch
- Changelog updated
- Builds verified (
yarn build) - User permission obtained to publish to npm
-
yarn release— version bump + tag pushed - GitHub Actions workflow triggered with correct tag and dist-tag
-
npm-publishenvironment approved - Workflow completed successfully
- Changelog published to GitHub Releases
- Team notified in Teams channel
- PR from release branch into
mainopened -
mainsynced back intodevelop -
git log origin/develop..origin/mainis empty
© epam, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .cursor/skills/release-workflow of epam/UUI.
Open the folder on GitHubat commit fd11393
Compare with similar skills
Uui Release Workflow next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Uui Release Workflow this skillepam/UUI | 248 | — | ~867 | Automated safety check: Pass | MIT | |
| Cline CLI Release Publishercline/cline | 70k | — | ~3.4k | Automated safety check: Warn | Apache-2.0 | |
| Cline Desktop App Releasecline/cline | 70k | — | ~4.5k | Automated safety check: Pass | Apache-2.0 | |
| Remotion Bits Releaseav/remotion-bits | 487 | — | ~1.2k | Automated safety check: Pass | None | |
| ZCF Release AutomationUfoMiao/zcf | 6.1k | — | ~3.4k | Automated safety check: Pass | MIT | |
| ClawRouter Release ChecklistBlockRunAI/ClawRouter | 6.6k | — | ~1.4k | Automated safety check: Pass | MIT |
Similar skills
Cline Desktop App Release
cline/cline
Covers preparing, tagging and publishing a Cline desktop app release on the stable, beta or nightly channel through the desktop-publish GitHub workflow.
Remotion Bits Release
av/remotion-bits
Runs the full release of the remotion-bits package: version bump, changelog, registry build, release commit, GitHub release, docs deploy and npm publish.
ZCF Release Automation
UfoMiao/zcf
Automates a version release with changesets: analyzes code changes, writes a bilingual CHANGELOG, bumps the version and commits through a release branch and pull request.
ClawRouter Release Checklist
BlockRunAI/ClawRouter
Walks the agent through every ClawRouter release step in order, from the version bump and changelog entry to build, tests, npm publish, git tag and GitHub release.
Release Process
GoogleCloudPlatform/genai-factory
Guide for cutting a new release of the GenAI Factory repository.
More from epam/UUI
All 10 skills in this repoUui Components
epam/UUI
Helps create and modify UUI (EPAM Unified UI) components following established patterns.
Uui Data Sources
epam/UUI
Helps work with UUI DataSources (ArrayDataSource, LazyDataSource, AsyncDataSource) powering PickerInput, DataTable, FiltersPanel, and other data-driven components.
Uui Documentation
epam/UUI
Helps update UUI documentation, add doc examples, configure Property Explorer, and manage component API documentation.
Uui E2E Testing
epam/UUI
Helps create and maintain E2E and screenshot tests for UUI components using Playwright.
Uui GitHub Issue Workflow
epam/UUI
Fetches GitHub issues from URLs and creates implementation plans for UUI.
Uui PR Contributing
epam/UUI
Guides the UUI pull request process including branch naming, pre-PR checklist, changelog updates, and quality requirements.
Related
Works with
Categories
Questions about Uui Release Workflow
What does Uui Release Workflow do?
Guides the UUI package release process including stable and beta releases, changelog updates, and handling failed releases. Uui Release Workflow is an agent skill from epam/UUI. Guides the UUI package release process including stable and beta releases, changelog updates, and handling failed releases.
When should I use Uui Release Workflow?
Uui Release Workflow fits situations like: releasing UUI packages; updating changelog; troubleshooting release issues.
How do I install Uui Release Workflow in Claude Code?
Run `npx skills add epam/UUI --skill uui-release-workflow -a claude-code`. Or copy the skill folder (.cursor/skills/release-workflow in epam/UUI) into .claude/skills/uui-release-workflow in your project. Claude Code loads it when a task matches its description.
How do I install Uui Release Workflow in Codex?
Run `npx skills add epam/UUI --skill uui-release-workflow -a codex`. Or copy the skill folder (.cursor/skills/release-workflow in epam/UUI) into .agents/skills/uui-release-workflow in your project. Codex loads it when a task matches its description.
Can I use Uui Release Workflow in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add epam/UUI --skill uui-release-workflow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/uui-release-workflow, .gemini/skills/uui-release-workflow, .github/skills/uui-release-workflow and .opencode/skills/uui-release-workflow in your project.
What does Uui Release Workflow need to run?
Going by SKILL.md and its folder, Uui Release Workflow needs the command-line tools its instructions call (yarn, git and lerna).
Does Uui Release Workflow access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Uui Release Workflow safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Uui Release Workflow use?
Uui Release Workflow is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Uui Release Workflow use?
About 867 tokens (SKILL.md is roughly 3.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Uui Release Workflow?
Skills that share tags, products or a category with Uui Release Workflow: Cline CLI Release Publisher (cline/cline, 70k stars), Cline Desktop App Release (cline/cline, 70k stars), Remotion Bits Release (av/remotion-bits, 487 stars) and ZCF Release Automation (UfoMiao/zcf, 6.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Uui Release Workflow?
epam (a GitHub organization) maintains it in epam/UUI, which has 248 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on September 29, 2026.
Source: epam/UUI on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.