Mecatl Release Cutting
stacklok/mecatl
Cuts a tagged mecatl release by dispatching the release-PR workflow, merging the bot's pull request and verifying the tag, images, Helm chart, signed archives and Homebrew formula.
Walks through releasing a new version of clickup-cli: pre-release checks, version bump, tagging, CI watch, release notes and the Homebrew update.
Install ClickUp CLI Release Process
The automated check flagged lines worth reading first. See the safety section below.
$ npx skills add krodak/clickup-cli --skill releasing-clickup-cli -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install krodak/clickup-cli releasing-clickup-cli --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/krodak/clickup-cli.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/releasing-clickup-cli .claude/skills/releasing-clickup-cli && 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 "releasing-clickup-cli" agent skill from https://github.com/krodak/clickup-cli/tree/main/.agents/skills/releasing-clickup-cli into .claude/skills/releasing-clickup-cli/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "releasing-clickup-cli", 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/krodak/clickup-cli/tree/main/.agents/skills/releasing-clickup-cliType 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 krodak/clickup-cli --skill releasing-clickup-cli -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install krodak/clickup-cli releasing-clickup-cli --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/krodak/clickup-cli.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/releasing-clickup-cli .agents/skills/releasing-clickup-cli && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "releasing-clickup-cli" agent skill from https://github.com/krodak/clickup-cli/tree/main/.agents/skills/releasing-clickup-cli into .agents/skills/releasing-clickup-cli/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "releasing-clickup-cli", 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 krodak/clickup-cli --skill releasing-clickup-cli -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install krodak/clickup-cli releasing-clickup-cli --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/krodak/clickup-cli.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/releasing-clickup-cli .cursor/skills/releasing-clickup-cli && 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 "releasing-clickup-cli" agent skill from https://github.com/krodak/clickup-cli/tree/main/.agents/skills/releasing-clickup-cli into .cursor/skills/releasing-clickup-cli/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "releasing-clickup-cli", 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/krodak/clickup-cli.git --path .agents/skills/releasing-clickup-cli--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 krodak/clickup-cli --skill releasing-clickup-cli -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install krodak/clickup-cli releasing-clickup-cli --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/krodak/clickup-cli.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/releasing-clickup-cli .gemini/skills/releasing-clickup-cli && 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 "releasing-clickup-cli" agent skill from https://github.com/krodak/clickup-cli/tree/main/.agents/skills/releasing-clickup-cli into .gemini/skills/releasing-clickup-cli/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "releasing-clickup-cli", 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 krodak/clickup-cli releasing-clickup-cliInstalls 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 krodak/clickup-cli --skill releasing-clickup-cli -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/krodak/clickup-cli.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/releasing-clickup-cli .github/skills/releasing-clickup-cli && 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 "releasing-clickup-cli" agent skill from https://github.com/krodak/clickup-cli/tree/main/.agents/skills/releasing-clickup-cli into .github/skills/releasing-clickup-cli/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "releasing-clickup-cli", 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 krodak/clickup-cli --skill releasing-clickup-cli -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install krodak/clickup-cli releasing-clickup-cli --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/krodak/clickup-cli.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/releasing-clickup-cli .opencode/skills/releasing-clickup-cli && 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 "releasing-clickup-cli" agent skill from https://github.com/krodak/clickup-cli/tree/main/.agents/skills/releasing-clickup-cli into .opencode/skills/releasing-clickup-cli/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "releasing-clickup-cli", 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
releasing-clickup-cli- GitHub stars
- 121
- Token cost
- ~906 tokens
- SKILL.md length
- 256 words
- Files
- 1
- Skills in repo
- 3
- Repo updated
- First seen
- Licence
- MIT
At a glance
Walks through releasing a new version of clickup-cli: pre-release checks, version bump, tagging, CI watch, release notes and the Homebrew update.
- Works in 9 steps: Commit feature/fix changes first → Bump version → Sync all version-tracked files → …
- Releasing a new version of clickup-cli
- SKILL.md covers Versioning, Pre-release checklist, Release steps and Common mistakes to avoid
- Calls git, npm and gh; reaches registry.npmjs.org
What it does
The skill is a release runbook for one project. It maps change types to bumps, with a bug fix as a patch, a backward-compatible feature as a minor and a breaking change as a major, and lists a pre-release checklist: typecheck, lint, tests including a version sync test, build, and registering any new commands in src/commands/metadata.ts. Feature commits stay separate from the version bump commit.
Release steps run npm version without a git tag, then a script that syncs version-tracked files such as docs/commands.md, the clickup-cli skill header and the Claude plugin manifest, followed by a commit and a v-prefixed tag. The agent then watches the release workflow with gh run watch; that workflow typechecks, tests, builds, publishes to npm and creates the GitHub release. Known CI failures are listed with fixes, including a peer dependency conflict, a missing completion entry and an already-published version.
Afterwards it writes release notes in a fixed style, with one level-two heading per feature, a code block with two or three examples, the test count at the bottom and no emojis, and updates the Homebrew tap. The excerpt ends before the Homebrew details.
When your agent uses it
- Releasing a new version of clickup-cli
- Bumping the version and syncing every file that tracks it
- Diagnosing a failed release workflow after tagging
- Writing release notes and updating the Homebrew tap
Example prompts
- “Release the next minor version of clickup-cli, and walk through the pre-release checklist first.”
- “The release workflow failed on npm publish saying the version is already published, so fix it.”
- “Write the GitHub release notes for the latest tag in the usual style.”
Requirements
- npm and Node.js
- GitHub CLI (gh) with access to the repository
- Access to the project's Homebrew tap
Workflow steps
9 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit a775de5. 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:
gitnpmghnodecurl
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
registry.npmjs.org
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
ClickUp CLI Release Process loads about 906 tokens when it runs. Until then it costs about 54 tokens; SKILL.md has 256 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: warnings
The automated check found patterns that need a careful read before installing.
- WarningMentions a credentials file (SSH keys, cloud or package-manager tokens)SKILL.md:72
t (typescript-eslint vs TypeScript 6). `.npmrc` has `legacy-peer-deps=true`.
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 krodak/clickup-cli at commit a775de5, republished under its MIT licence (© krodak). 256 words, ~906 tokens.
Download SKILL.mdSave it as
.claude/skills/releasing-clickup-cli/SKILL.md (or your agent's skills folder).- name
- releasing-clickup-cli
- description
- Publishes a new version of clickup-cli to npm, updates Homebrew tap, writes release notes, and syncs the agent skill. Use when releasing a new version, bumping version, or verifying a release.
- metadata.internal
- true
Versioning
| Change type | Bump |
|---|---|
| Bug fix | patch (x.y.Z) |
| New feature, backward compatible | minor (x.Y.0) |
| Breaking change | major (X.0.0) |
Pre-release checklist
-
npm run typecheckpasses -
npm run lintpasses -
npm testpasses (includes version sync test) -
npm run buildsucceeds - New commands added to
src/commands/metadata.ts(completion test will fail otherwise)
Release steps
1. Commit feature/fix changes first
Do NOT mix feature commits with version bump commits.
2. Bump version
npm version <version> --no-git-tag-version3. Sync all version-tracked files
node --import tsx scripts/sync-command-docs.tsThis updates:
docs/commands.mdquick reference tableskills/clickup-cli/SKILL.mdversion header (line 6)skills/clickup-cli/SKILL.mdversion check hint (line 10).claude-plugin/plugin.jsonversion field
The version synchronization test in tests/unit/ verifies these stay in sync.
4. Commit and tag
git add package.json package-lock.json .claude-plugin/plugin.json docs/commands.md skills/clickup-cli/SKILL.md
git commit -m "bump v<version>"
git tag v<version>
git push origin main --tags5. Wait for CI
gh run watch --repo krodak/clickup-cli --exit-status $(gh run list --repo krodak/clickup-cli --workflow release.yml --limit 1 --json databaseId -q '.[0].databaseId')The release workflow runs: typecheck, test, build, npm publish (OIDC), GitHub Release creation.
6. If CI fails
Common failures:
npm cifails: peer dep conflict (typescript-eslint vs TypeScript 6)..npmrchaslegacy-peer-deps=true.- Completion test fails:
metadata.tsis missing a new command or flag. Add it, amend, re-tag, force push. - npm publish fails "already published": Version already exists on npm from a previous attempt. Bump to next version.
Fix, then:
git commit --amend --no-edit # or new commit
git tag -d v<version>
git tag v<version>
git push origin main --tags --force7. Write release notes
gh release edit v<version> --repo krodak/clickup-cli --notes "$(cat <<'EOF'
## Heading
Description and code examples.
Test count.
EOF
)"Style: H2 per feature, code block with 2-3 examples, test count at bottom, no emojis.
8. Update Homebrew
SHA=$(curl -sL https://registry.npmjs.org/@krodak/clickup-cli/-/clickup-cli-<version>.tgz | shasum -a 256 | cut -d' ' -f1)Then update ~/repositories/homebrew-tap/Formula/clickup-cli.rb:
- Change version in URL
- Change sha256
git -C ~/repositories/homebrew-tap add Formula/clickup-cli.rb
git -C ~/repositories/homebrew-tap commit -m "clickup-cli <version>"
git -C ~/repositories/homebrew-tap push origin main9. Install updated skill
cp skills/clickup-cli/SKILL.md ~/.config/opencode/skills/clickup/SKILL.mdCommon mistakes to avoid
- Running
git commitbeforenode --import tsx scripts/sync-command-docs.ts(use the script to sync everything) - Not adding new commands to
src/commands/metadata.ts - Bumping version in the same commit as feature changes
- Force-pushing tags without deleting old tag first
© krodak, 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 .agents/skills/releasing-clickup-cli of krodak/clickup-cli.
Open the folder on GitHubat commit a775de5
Compare with similar skills
ClickUp CLI Release Process 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 |
|---|---|---|---|---|---|---|
| ClickUp CLI Release Process this skillkrodak/clickup-cli | 121 | — | ~906 | Automated safety check: Warn | MIT | |
| Mecatl Release Cuttingstacklok/mecatl | 250 | — | ~3.9k | Automated safety check: Pass | Apache-2.0 | |
| OpenWork Release Processdifferent-ai/openwork | 24k | — | ~2.3k | Automated safety check: Pass | Custom licence | |
| Cline CLI Release Publishercline/cline | 70k | — | ~3.4k | Automated safety check: Warn | Apache-2.0 | |
| ClawRouter Release ChecklistBlockRunAI/ClawRouter | 6.6k | — | ~1.4k | Automated safety check: Pass | MIT | |
| AnyDrag Release RoutineXueshiQiao/AnyDrag | 227 | — | ~2.6k | Automated safety check: Pass | GPL-3.0 |
Similar skills
OpenWork Release Process
different-ai/openwork
Cuts an OpenWork desktop release through a tag-driven GitHub Actions workflow that makes no commits, with pre-tag checks on open fix PRs and verification afterward.
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.
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.
AnyDrag Release Routine
XueshiQiao/AnyDrag
Runs the full AnyDrag release process end to end, from cumulative bilingual release notes through version bumping to watching CI and the Homebrew cask update.
Kt Search Release
jillesvangurp/kt-search
A skill your agent uses when the user wants to cut, publish, tag, or create a GitHub release for kt-search, especially when the task includes version bumping, validating that commits are pushed…
More from krodak/clickup-cli
ClickUp CLI Testing
krodak/clickup-cli
Explains how to run and extend the clickup-cli tests: unit tests with a mocked client, e2e tests against a real ClickUp workspace, and the fixture data they rely on.
ClickUp CLI
krodak/clickup-cli
Lets your agent read and change ClickUp tasks, sprints, comments, Docs, Chat, views and webhooks through the cup command-line tool.
Related
Categories
Questions about ClickUp CLI Release Process
What does ClickUp CLI Release Process do?
Walks through releasing a new version of clickup-cli: pre-release checks, version bump, tagging, CI watch, release notes and the Homebrew update. The skill is a release runbook for one project.ts.
When should I use ClickUp CLI Release Process?
ClickUp CLI Release Process fits situations like: releasing a new version of clickup-cli; bumping the version and syncing every file that tracks it; diagnosing a failed release workflow after tagging; writing release notes and updating the Homebrew tap.
How do I install ClickUp CLI Release Process in Claude Code?
Run `npx skills add krodak/clickup-cli --skill releasing-clickup-cli -a claude-code`. Or copy the skill folder (.agents/skills/releasing-clickup-cli in krodak/clickup-cli) into .claude/skills/releasing-clickup-cli in your project. Claude Code loads it when a task matches its description.
How do I install ClickUp CLI Release Process in Codex?
Run `npx skills add krodak/clickup-cli --skill releasing-clickup-cli -a codex`. Or copy the skill folder (.agents/skills/releasing-clickup-cli in krodak/clickup-cli) into .agents/skills/releasing-clickup-cli in your project. Codex loads it when a task matches its description.
Can I use ClickUp CLI Release Process 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 krodak/clickup-cli --skill releasing-clickup-cli -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/releasing-clickup-cli, .gemini/skills/releasing-clickup-cli, .github/skills/releasing-clickup-cli and .opencode/skills/releasing-clickup-cli in your project.
What does ClickUp CLI Release Process need to run?
Going by SKILL.md and its folder, ClickUp CLI Release Process needs the command-line tools its instructions call (git, npm, gh, node and curl). Our summary lists: npm and Node.js; GitHub CLI (gh) with access to the repository; Access to the project's Homebrew tap.
Does ClickUp CLI Release Process access the network?
SKILL.md names 1 domain. In commands or code: registry.npmjs.org; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Is ClickUp CLI Release Process safe to install?
Our automated static check of SKILL.md flagged 1 warning(s): mentions a credentials file (ssh keys, cloud or package-manager tokens). Read the flagged lines before installing; the check is not a guarantee either way.
What licence does ClickUp CLI Release Process use?
ClickUp CLI Release Process 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 ClickUp CLI Release Process use?
About 906 tokens (SKILL.md is roughly 3.6k 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 ClickUp CLI Release Process?
Skills that share tags, products or a category with ClickUp CLI Release Process: Mecatl Release Cutting (stacklok/mecatl, 250 stars), OpenWork Release Process (different-ai/openwork, 24k stars), Cline CLI Release Publisher (cline/cline, 70k stars) and ClawRouter Release Checklist (BlockRunAI/ClawRouter, 6.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains ClickUp CLI Release Process?
krodak (a GitHub user) maintains it in krodak/clickup-cli, which has 121 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on October 6, 2026.
Source: krodak/clickup-cli on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.