Menu
Use when preparing, validating, tagging, or pushing a yeet patch release.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Use for yeet CLI operations like deploying or updating services, restarting/removing services, installing or upgrading catch on a host, checking status/logs/info, and guidance on CATCH_HOST/--host targeting.
Use when changing Docker compose deployment, docker pull/update/outdated behavior, internal registry image handling, Docker networking, or digest comparison logic.
Use when choosing verification commands, working on tests, quality tooling, race/fuzz/mutation checks, pre-commit failures, or release-quality gates.
Use when changing yeet client command routing, catch remote execution, catchrpc types, or the boundary between local CLI parsing and catch-side parsing.
Use when user-facing CLI behavior, flags, workflows, README examples, website manual pages, or changelog entries need to be updated.
Basé sur la classification professionnelle SOC
| name | yeet-release |
| description | Use when preparing, validating, tagging, or pushing a yeet patch release. |
Use this skill for release work. Follow root AGENTS.md exactly.
vX.Y.Z tag and choose the next patch version.website/docs/changelog.mdx with a date section, version heading, and
1-3 user-facing bullets. Follow .codex/skills/yeet-docs/SKILL.md for
changelog wording: the latest version must stand alone for users, and
corrective release plumbing must not be the release note.website/.website submodule pointer in the root repo.git tag -a vX.Y.Z -m "vX.Y.Z"
origin/main through the root AGENTS.md
finish-to-main flow, then push the tag.git status --short --branch
git -C website status --short --branch
git rev-parse HEAD:website
git -C website rev-parse HEAD
git tag --list 'v*' --sort=-version:refname | sed -n '1,5p'
git ls-remote --tags origin vX.Y.Z
Do not commit, tag, or push without explicit user authorization.