agentleFS
Sign inStart free
krodakkrodak/clickup-cli/.agents/skills/releasing-clickup-cli/SKILL.md

releasing-clickup-cli

Skill123 starsChanged 38 days agoMITView on GitHub

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.

  • Pipes a download into a shell
  • Commits and pushes

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do NOT mix feature commits with version bump commits.

    line 28
  2. Very specific:

    Not adding new commands to src/commands/metadata.ts

    line 126

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Versioning

Change typeBump
Bug fixpatch (x.y.Z)
New feature, backward compatibleminor (x.Y.0)
Breaking changemajor (X.0.0)

Pre-release checklist

  • npm run typecheck passes
  • npm run lint passes
  • npm test passes (includes version sync test)
  • npm run build succeeds
  • 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-version

3. Sync all version-tracked files

node --import tsx scripts/sync-command-docs.ts

This updates:

  • docs/commands.md quick reference table
  • skills/clickup-cli/SKILL.md version header (line 6)
  • skills/clickup-cli/SKILL.md version check hint (line 10)
  • .claude-plugin/plugin.json version 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 --tags

5. 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 ci fails: peer dep conflict (typescript-eslint vs TypeScript 6). .npmrc has legacy-peer-deps=true.
  • Completion test fails: metadata.ts is 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 --force

7. 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 main

9. Install updated skill

cp skills/clickup-cli/SKILL.md ~/.config/opencode/skills/clickup/SKILL.md

Common mistakes to avoid

  • Running git commit before node --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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free