菜单
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.
用 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 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).
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 | deploy |
| description | 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. |
Ship the current work as a preview: main → CI preview build → brew llmux-preview
→ local. For a local-only dev loop use build; for a stable release use release.
Shared mechanics: .claude/skills/_shared/cd-reference.md (procedure A = hot-deploy,
procedure B = publish+verify brew).
just check green; know what's uncommitted (git status). If dirty, ask
whether to commit (and the message) or stash. (Decision point.)git push origin main (token fallback if needed).rid=$(gh run list --repo 2lab-ai/llmux --workflow preview.yml -L1 --json databaseId -q '.[0].databaseId')
gh run watch --repo 2lab-ai/llmux "$rid" --exit-status
preview-<YYYY-MM-DD-HHMM>-<sha12>.gh release list --repo 2lab-ai/llmux -L5 (preview is a
prerelease — gh release view without a tag shows the stable one, not this). Note the
new preview-* tag.formula=llmux-preview. Dispatch the tap
bump.yml, watch it, brew update && brew upgrade llmux-preview, confirm the brew
version (YYYY.MM.DD.HHMM) matches the new preview tag's timestamp./opt/homebrew/bin/llmux restart. Verify --version reports (preview <id>)./opt/homebrew/bin/llmux status — daemon on the new preview build.bump.yml or brew stays stale.gh release view hiding the prerelease (shows stable) — use gh release list.brew update first, re-check brew info.gh run watch, don't assume instant.