deploy
Skill10 starsChanged 40 days agoMITView on GitHub
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.
- Commits and pushes
161 other projects use a version of this.
Adopted by
Most recently taken up by
- krystaleicher/claude-skillstheir own version, first seen Nov 16, 2026
- KazKato91/roomi-claude-plugintheir own version, first seen Nov 16, 2026
- AlejandroGodius/claude-skillstheir own version, first seen Nov 16, 2026
- reloru/new-relotheir own version, first seen Nov 16, 2026
- maxwell2732/claudecode-research-harness-workflowtheir own version, first seen Nov 15, 2026
- patrickjaja/claude-desktop-extratheir own version, first seen Nov 15, 2026
Used with
Projects with it also use pm-discovery, qa-phase and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
ww-w-aiSkillpm-discovery
PM Agent Team - Automated product discovery, strategy, and PRD generation. Runs PM analysis workflow to produce comprehensive PRD before PDCA Plan phase.
Also in 3 projects that use this
ww-w-aiSkillqa-phase
Run QA tests at various levels (L1-L5) for features under PDCA management. Integrates with MCP tools to execute structured test plans.
Also in 3 projects that use this
- +10 more from ww-w-ai
Other versions161 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 161
- ok-oldking/ok-wuthering-waves★ 8.6ksame name
- memovai/mimiclaw★ 5.8ksame name
- KingKongRobotics/jumper★ 3.1ksame name
- jhd3197/ServerKit★ 1.8ksame name
- pedrohcgs/claude-code-my-workflow★ 1.7ksame name
- mattmireles/gemma-tuner-multimodal★ 1.5ksame name
- microsoft/power-platform-skills★ 1.2ksame name
- jazzyalex/agent-sessions★ 948same name
- awslabs/agent-plugins★ 943same name
- patrickjaja/claude-desktop-extra★ 761same name
151 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository7 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- agent-loopSkill
- agent-resolveSkill
- agent-triageSkill
- buildSkill
- releaseSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 143 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 18
Land on main: If on a branch, merge/fast-forward into main per repo norm.
“Common” is measured: kept by at least 6 in 10 of the 143 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
deploy (배포) — preview channel
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).
Steps
- Pre-flight.
just checkgreen; know what's uncommitted (git status). If dirty, ask whether to commit (and the message) or stash. (Decision point.) - Land on main. If on a branch, merge/fast-forward into main per repo norm.
Confirm with the user before pushing main (public preview channel), then
git push origin main(token fallback if needed). - Watch the preview build.
Success publishes prereleaserid=$(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-statuspreview-<YYYY-MM-DD-HHMM>-<sha12>. - Confirm the prerelease.
gh release list --repo 2lab-ai/llmux -L5(preview is a prerelease —gh release viewwithout a tag shows the stable one, not this). Note the newpreview-*tag. - Publish + verify brew — procedure B with
formula=llmux-preview. The previewpublishjob automatically pushes the matching formula/cask to the tap. Confirm the exact tag there, thenbrew update && brew upgrade llmux-preview; confirm the brew version (YYYY.MM.DD.HHMM) matches the new preview tag's timestamp. - Hot-deploy + restart. The brew build is already in the Cellar after upgrade, so:
/opt/homebrew/bin/llmux restart. Verify--versionreports(preview <id>). - Verify.
/opt/homebrew/bin/llmux status— client and daemon on the new preview build. For frontend/runtime changes, execute the shared reference’s installed native-Codex and Claude-SDK tool smokes, with daemon Node/npm available. - Report preview tag, brew version, running daemon version.
Common mistakes
- Treating a release asset alone as publication: preview
publishmust also pass its automatic tap bump. Diagnose and rerun its idempotent publish job on failure; the tap’s manual dispatch currently targets Dbotter and skips llmux jobs. - Rebuilding/restarting unchanged runtime for docs-only followups: follow the shared
reference’s reviewed
[skip ci]documentation path instead. gh release viewhiding the prerelease (shows stable) — usegh release list.- "Already up-to-date" after a bump →
brew updatefirst, re-checkbrew info. - CI latency — poll with
gh run watch, don't assume instant.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

