메뉴
Prepare and ship a Untether release. Use when asked to cut a release, bump release versions, update changelog/spec/readme, tag v<major.minor.patch>, or trigger the GitHub release workflow.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Release workflow for Untether — issue audit, version decisions, changelog drafting, pre-release validation, tagging, and post-release verification. Use when preparing a release or debugging release failures.
Untether overall architecture, event model, data flow, config system, engine backend registration, progress tracking, approval notifications, ephemeral cleanup, and key abstractions. Use when working on core infrastructure or understanding how the pieces fit together.
Claude Code CLI stream-json protocol as consumed by Untether. Covers JSONL event types, content blocks, control channel protocol, permission modes, auto-approve, progressive cooldown, and ExitPlanMode handling. This is the CONSUMER side — Untether spawns Claude Code as a subprocess.
Raw Telegram Bot API patterns used by Untether. Covers httpx async HTTP client, inline keyboards, callback queries, long polling, rate limiting, outbox model, forum topics, voice transcription, and media group coalescing. NOT aiogram, python-telegram-bot, or grammY — Untether uses raw HTTP.
Codex CLI, OpenCode CLI, and Pi CLI runner protocols for Untether. Covers JSONL event types, event translation, resume mechanisms, and key differences between engines. All three are non-interactive (no control channel).
JSONL subprocess management patterns for Untether engine runners. Covers JsonlSubprocessRunner base class, template methods, event translation, session locking, resume tokens, process lifecycle, PTY usage, and concurrent session registries.
| name | untether-release |
| description | Prepare and ship a Untether release. Use when asked to cut a release, bump release versions, update changelog/spec/readme, tag v<major.minor.patch>, or trigger the GitHub release workflow. |
Prepare a tagged release that matches the GitHub Actions release workflow. The workflow requires the tag version to match both pyproject.toml and src/untether/__init__.py.
Pick the release version (major.minor.patch) and the release date (YYYY-MM-DD) for changelog/spec headers.
If the current version has a .dev suffix, assume the target release version is the same version without the suffix, as long as that tag does not already exist.
Update changelog.md by adding a new top section. Before writing it, study the diff between the previous tag and the new release to rank changes; put user-facing changes first.
## v<major.minor.patch> (YYYY-MM-DD)changes, fixes, breaking, docs as needed.Update version strings to match the release tag:
pyproject.toml: project.version = "<major.minor.patch>"src/untether/__init__.py: __version__ = "<major.minor.patch>"uv.lock: refresh so the root package version matches (run uv lock or uv sync).Update docs/specification.md to match the release:
# Untether Specification v<major.minor.patch> [YYYY-MM-DD]Untether v<old> and Out of scope for v<old> lines with the new version.- No normative changes; align spec version with the v<major.minor.patch> release. unless the spec itself changed.If the release highlights new features, update readme.md accordingly (see v0.9.0 release).
Run the standard checks before committing:
just check (ruff/ty/pytest)Commit the release using conventional commits:
chore(release): v<major.minor.patch>git tag v<major.minor.patch>Push the tag to trigger .github/workflows/release.yml (build, PyPI publish, GitHub release).
If you keep a dev version between releases, bump the minor version (reset patch to 0) and commit (chore: bump version to ...).
pyproject.toml and src/untether/__init__.py.changelog.md and docs/specification.md.