Menu
Prepare an assembly CLI release — confirm main is green, then tag (locally or via the manual workflow) to trigger the bottle pipeline. Use when cutting a new release.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Use the AssemblyAI CLI (`assembly`) from the command line — transcribe audio/video files, URLs, and YouTube/podcast links; stream live real-time transcription from a mic/file/system audio; run full-duplex voice agents; query the LLM Gateway over transcripts; browse transcript and streaming-session history; sign in and manage account balance, usage, rate limits, API keys, and audit logs; scaffold a starter app (init); diagnose setup (doctor); and set up your coding agent's AssemblyAI docs MCP + skills (setup). Use whenever an agent is invoking the `assembly` command.
Run the full local verification gate for the assembly CLI (the same checks CI runs). Use before pushing or opening a PR.
Plan a new assembly CLI feature the way this repo does — drive the superpowers planning skill, then persist the spec + plan into docs/superpowers/ under this repo's naming and verification conventions. Use before building anything non-trivial.
| name | release-prep |
| description | Prepare an assembly CLI release — confirm main is green, then tag (locally or via the manual workflow) to trigger the bottle pipeline. Use when cutting a new release. |
| disable-model-invocation | true |
Drive an assembly release to a verified, tagged state. Stop and report at the first failure — never tag on a red check.
pyproject.toml / aai_cli/__init__.py string to bump. cut_release.sh defaults to the next patch above the latest vX.Y.Z tag; pass X.Y.Z for a minor/major bump../scripts/check.sh
Must end with All checks passed. (ruff, mypy, markdownlint, shellcheck, pytest+coverage, build, twine check --strict). The release builds whatever main points at, so confirm main is green before tagging.
Two equivalent ways to cut the tag — both land on .github/workflows/release.yml:
Local (from a clean main in sync with origin/main):
./scripts/cut_release.sh # next patch; --dry-run verifies without tagging, --yes skips the prompt
./scripts/cut_release.sh 0.3.0 # explicit version
No local checkout (e.g. a Claude web session on a feature branch): run the Release workflow's manual workflow_dispatch — GitHub's "Run workflow" button, or the actions_run_trigger MCP tool — with an optional version input (blank = next patch). Its tag job resolves the version and creates+pushes the tag from main, then the same run builds and publishes. Set dry_run: true to build the bottle for an existing tag without publishing.
The tag triggers .github/workflows/release.yml, which:
arm64_sonoma).vX.Y.Z GitHub Release with the bottle attached.release/vX.Y.Z-formula PR pinning the formula to the tag's source and adding the bottle do block.Review the release/vX.Y.Z-formula PR (formula-only diff) and merge it with the repo-admin "merge without waiting for requirements" override — a PR opened by GITHUB_TOKEN doesn't trigger CI, so the required check won't report on its own.
On a clean arm64 Mac:
brew update && brew install assembly # pulls the bottle — fast, no rust/llvm
assembly --version # matches the tagged version
The PyPI name assemblyai-cli is squatted by a third party — pip install assemblyai-cli does not resolve to this project. Distribution is the Homebrew bottle (primary, macOS arm64) and pipx/uv git+https (fallback, all platforms). There is no PyPI publish step.