メニュー
Use for normal llmux dev iteration when the user says "빌드", "빌드해줘", "build", "build and deploy locally", or wants to compile + run a change locally and save it. Builds release, hot-deploys the binary to the local daemon, commits, and pushes to a feature branch (never main).
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when the user says "resolve", "해결해줘", "픽스해줘", or wants to take one ready-to-agent llmux issue/PR, implement the fix on its branch, get `just check` green, and hand back a review-ready PR. Does NOT merge or deploy by default.
Use when the user says "triage", "이슈 정리", "분류", or wants to scan open llmux GitHub issues, decide which are safe for an agent to implement, label them, and open a tracking branch + draft PR for each ready one. Reads and labels issues; never writes source code.
Use when the user says "배포", "배포해줘", "deploy", or "ship a preview" for llmux. Pushes to main, lets CI publish a preview prerelease, refreshes the llmux-preview brew formula, verifies brew actually updated, then hot-deploys that build locally and restarts.
Use when the user says "릴리즈", "릴리즈해줘", "release", "cut a release", or "stable release" for llmux. Bumps the version, tags v*, lets CI publish the stable GitHub release, refreshes the llmux stable brew formula, verifies brew updated, hot-deploys + restarts locally, and verifies client + server with llmux status.
Use when the user says "loop", "반복", "쭉 돌려줘", or wants to run triage then resolve repeatedly until there are no agent-workable llmux issues/PRs left. Thin orchestrator over the agent-triage and agent-resolve skills; dry-run by default.
| name | build |
| description | Use for normal llmux dev iteration when the user says "빌드", "빌드해줘", "build", "build and deploy locally", or wants to compile + run a change locally and save it. Builds release, hot-deploys the binary to the local daemon, commits, and pushes to a feature branch (never main). |
Normal dev-loop runbook: compile a release binary, hot-deploy it to the running local
daemon, commit, and push to a feature branch (never main — that triggers a public
preview). For preview/stable channels use the deploy / release skills instead.
Shared mechanics: .claude/skills/_shared/cd-reference.md (procedure A = hot-deploy).
git rev-parse --abbrev-ref HEAD. If on main, ask the
user for a branch name (or propose feat/<short-desc>) and git switch -c <branch>.
(Decision point: branch name needs the user.)just check (fmt + clippy -D warnings + tests) must be green before committing.
Fix failures; do not commit red.cargo build --release --locked; rm the read-only Cellar file; cp; chmod 755;
llmux restart). Autonomous — this is the whole point of build./opt/homebrew/bin/llmux status — daemon back up on the new binary,
in_flight was 0 before restart.git add -A && git commit -m "<type>: <summary>".git push -u origin <branch>. On a stale ghs_
token, use the gh auth token fallback (shared reference).cp over the read-only Cellar binary → EACCES. rm -f "$(readlink -f /opt/homebrew/bin/llmux)" first (procedure A).build — that fires the preview pipeline. Branch only.just check red, or with an emoji / AI co-author line.brew upgrade will overwrite this hot-deployed dev dev binary — expected;
re-run build to restore.