Skip to content
Skills Library
DevOps & cloud · Automation

release-cli

/release-cli

Release a new version of the pd CLI. Runs tests, bumps version, creates git tag, and pushes to remote. Use when releasing a new CLI version.

Repository
pondorasti ↗
Licence
MIT
Last repository change
27.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Release a new version of the pd CLI. Runs tests, bumps version, creates git tag, and pushes to remote. Use when releasing a new CLI version.

Original author description

Release a new version of the pd CLI. Runs tests, bumps version, creates git tag, and pushes to remote. Use when releasing a new CLI version.

How it works

  1. Pre-flight Checks
  2. Step 1: Run Tests
  3. Step 2: Bump Version
  4. Step 3: Commit Version Bump
  5. Step 4: Create and Push Tag
  6. Step 5: Monitor CI
  7. Step 6: Smoke Test Published Package
  8. Troubleshooting
Original SKILL.md headings · 112 lines, 311 words
SKILL.md preview
---
name: release-cli
description: Release a new version of the pd CLI. Runs tests, bumps version, creates git tag, and pushes to remote. Use when releasing a new CLI version.
---

# CLI Release Process

Follow these steps to release a new version of the `pd` CLI.

## Pre-flight Checks

Before starting:

1. Verify you're on the `main` branch
2. Ensure working tree is clean (no uncommitted changes)
3. Pull latest changes

```bash
git status
git branch --show-current
git pull origin main
```

## Step 1: Run Tests

Ensure all tests pass before releasing:

```bash
bun test
```

Working directory: `packages/cli`

If tests fail, fix them before proceeding.

## Step 2: Bump Version

Bump the patch version in `packages/cli/package.json` (e.g., 0.1.27 → 0.1.28).

## Step 3: Commit Version Bump

```bash
git add packages/cli/package.json
git commit -m "chore: bump cli vX.Y.Z"
```

Replace `X.Y.Z` with the new version.

## Step 4: Create and Push Tag

```bash
git tag vX.Y.Z
git push origin main
git push origin vX.Y.Z
```

## Step 5: Monitor CI

Watch the release workflow and wait for it to finish before continuing:

```bash
gh run list --workflow Release --limit 1
gh run watch
```

If no run shows up yet, wait a moment and retry until it appears:

```bash
sleep 10
gh run list --workflow Release --limit 1
```

If the workflow fails, inspect logs:

```bash
gh run view --log-failed
```

## Step 6: Smoke Test Published Package

Run a quick smoke test from the registry:

```bash
npx pondorasti@X.Y.Z --help
bun pm view pondorasti version
```

Confirm `bun pm view` returns `X.Y.Z`.

Use `npx` for the install smoke test because `bunx` can intermittently fail to resolve freshly published exact versions even when npm metadata is already updated.

Note: the public package name is `pondorasti` (unscoped), not `@pondorasti/cli`.

## Troubleshooting

### Tests Fail

Fix failing tests before releasing.

### Tag Already Exists

Delete the tag and retry:

```bash
git tag -d vX.Y.Z
git push origin :refs/tags/vX.Y.Z
```

### Push Rejected

Pull latest and retry:

```bash
git pull --rebase origin main
```

Versions

RepositoryScoreLicence
This page · pondorasti/pondorasti100MIT
velimirmueller/ai-development-skills100MIT

Database snapshot: 13.11.2026 · package version 547b181cf744 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100version-release
    Use when bumping version, creating a release tag, or pushing a version tag. Triggers on "version up", "release", "tag push", "bump version".
  • 95release
    Releases a new version of my-skills-anywhere. Bumps the semver version in the plugin manifest, runs the unit tests, the manifest checks and the verify skill, checks commit identities, commits, tags, and pushes only on the owner's explicit yes. Use when asked to release, cut a…
  • 100release
    Cut a new release of ra-mcp. Determines the next version from the commit history since the last tag, bumps pyproject.toml, commits, tags, and pushes. Use when: "make a release", "cut a release", "release", "bump version", "tag a new version", "publish a new version".
  • 100create-new-release
    Create and push a new semver release tag. Asks for release type (patch/minor/major), validates commit exists on remote, bumps version, and pushes the tag.
  • 100release
    Cut a release of pyhubblenetwork — bumps version, generates release notes from commits, commits, tags, and pushes to trigger the PyPI release workflow. Use this skill when the user wants to release, publish, cut a release, bump version, or push a new version to PyPI. Invoke via /release.
  • 100release
    Release the scratch CLI or the pi package: bump, tag, GitHub release, CI publishes to npm. Use for "release", "publish", "bump version" or "release candidate".

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.