agentleFS
2lab-ai2lab-ai/llmux/.claude/skills/deploy/SKILL.md

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

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-aiSkill

    pm-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-aiSkill

    qa-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

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
  1. Distinctive:

    Land on main: If on a branch, merge/fast-forward into main per repo norm.

    line 18

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

  1. Pre-flight. just check green; know what's uncommitted (git status). If dirty, ask whether to commit (and the message) or stash. (Decision point.)
  2. 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).
  3. Watch the preview build.
    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
    Success publishes prerelease preview-<YYYY-MM-DD-HHMM>-<sha12>.
  4. Confirm the prerelease. 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.
  5. Publish + verify brew — procedure B with formula=llmux-preview. The preview publish job automatically pushes the matching formula/cask to the tap. Confirm the exact tag there, then brew update && brew upgrade llmux-preview; confirm the brew version (YYYY.MM.DD.HHMM) matches the new preview tag's timestamp.
  6. Hot-deploy + restart. The brew build is already in the Cellar after upgrade, so: /opt/homebrew/bin/llmux restart. Verify --version reports (preview <id>).
  7. 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.
  8. Report preview tag, brew version, running daemon version.

Common mistakes

  • Treating a release asset alone as publication: preview publish must 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 view hiding the prerelease (shows stable) — use gh release list.
  • "Already up-to-date" after a bump → brew update first, re-check brew info.
  • CI latency — poll with gh run watch, don't assume instant.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.