Menu
Use when releasing a new Ravi CLI version — version bump, tagging, and verification
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/ravi-hq/cli --skill releaseThe command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
Use when working with the Ravi CLI — identity, inbox, passwords, secrets, email, SMS, calls, and feedback commands
Use when testing CLI changes against the local backend before committing. Covers building with local endpoint, authenticating, and driving every command group with verification.
Use when generating a Go test file for a module following Ravi CLI test conventions
Showing SKILL.md
| name | release |
| description | Use when releasing a new Ravi CLI version — version bump, tagging, and verification |
Guide the release process for a new CLI version. This is a checklist — the user drives each step.
The user should specify the version to release (e.g., "release 0.4.0").
git status # Must be clean, on main branch
git log --oneline -5 # Review recent commits
make test # All tests must pass
make lint # No lint errors
make build API_URL=https://ravi.id
./bin/ravi version # Confirm version output
git log $(git describe --tags --abbrev=0)..HEAD --oneline --no-decorate
Review for any breaking changes that need documentation.
git tag v<VERSION> # e.g., git tag v0.4.0
git push origin v<VERSION> # Triggers GitHub Actions release workflow
gh run list --limit 1 # Find the triggered run
gh run watch # Watch it complete
The workflow automatically:
ravi-hq/homebrew-tapgh release view v<VERSION> # Check release was created
Confirm:
gh api repos/ravi-hq/homebrew-tap/commits --jq '.[0].commit.message'
Should show: ravi <VERSION>
If something goes wrong:
# Delete the tag locally and remotely
git tag -d v<VERSION>
git push origin :refs/tags/v<VERSION>
# Delete the GitHub release (if created)
gh release delete v<VERSION> --yes
| OS | Arch | Binary Name |
|---|---|---|
| macOS | arm64 | ravi-darwin-arm64 |
| macOS | amd64 | ravi-darwin-amd64 |
| Linux | arm64 | ravi-linux-arm64 |
| Linux | amd64 | ravi-linux-amd64 |
Note: Windows (amd64) is built by the Makefile but NOT included in the release workflow.