Menu
Use when changing yeet client command routing, catch remote execution, catchrpc types, or the boundary between local CLI parsing and catch-side parsing.
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.
Based on SOC occupation classification
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 preparing, validating, tagging, or pushing a yeet patch release.
Use when user-facing CLI behavior, flags, workflows, README examples, website manual pages, or changelog entries need to be updated.
| name | yeet-rpc |
| description | Use when changing yeet client command routing, catch remote execution, catchrpc types, or the boundary between local CLI parsing and catch-side parsing. |
Use this skill for command-routing and remote-exec work.
cmd/yeet parses global flags and group routing.cmd/yeet/cli_bridge.go resolves service arguments and <svc>@<host>.pkg/yeet decides whether a command is local or forwarded remotely.catchrpc.Exec carries command args to catch.pkg/catch is authoritative for parsing and executing remote commands.pkg/cli.mise exec -- go test ./pkg/cli ./cmd/yeet ./pkg/yeet -count=1
mise exec -- go test ./pkg/catch ./pkg/catchrpc -count=1