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

build

Skill10 starsChanged 40 days agoMITView on GitHub

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

  • Commits and pushes

167 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use backprop, finances 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.
  • JuliusBrusseeSkill

    backprop

    Bug → spec protocol. When a bug is found or a test fails, trace the cause, decide whether a new §V invariant would catch recurrence, append to §B. This is the one non-obvious thing SDD does that plan-then-execute doesn't. Triggers on test failure, bug report, post-mortem, or explicit user ask.

    Also in 4 projects that use this

  • GerardoRdz96Skill

    finances

    Use when Gera talks about his money — logging an expense ("I spent X on Y"), checking where he stands this pay-period, closing a period, planning debt payoff, onboarding his financial picture, or asking for budgeting/finance opinions. Servy's financial brain. Triggers — "I spent", "log this expense", "where am I this period", "close the period", "how's my budget", "debt plan", "should I pay off", "finances onboard", "/finances".

    Also in 3 projects that use this

  • cpiprintSkill

    favicon

    Generate favicons from a source image

    Also in 3 projects that use this

  • madeehahassanSkill

    Go-Live

    Pre-launch checklist. Use before making any app public, sharing a link externally, or announcing a product launch. Adapts to Claude Code, claude.ai, and Cowork.

    Also in 3 projects that use this

  • JuliusBrusseeSkill

    deepen

    Optional design-improvement pass for when you have spare usage to drain. Finds the shallowest modules in the code the spec touches, researches a deeper design, and proposes refactors that shrink interfaces and hide decisions — behavior held constant, tests green before and after. Proposes §I/§V/§T edits, never silent rewrites. Triggers when the user says "deepen this", "improve the design", "this module feels shallow", "pull complexity down", "use spare budget on the codebase", or invokes /ck:deepen. Leans on the codebase-design skill's deep-module vocabulary when present.

    Also in 3 projects that use this

  • synaptiaiSkill

    gate

    Create a BDSK review_gate artifact. Defines a checkpoint that controls whether generated output may proceed toward acceptance. Use when defining quality, security, or scope gates for execution plans.

    Also in 5 projects that use this

The file

Files
SKILL.md

build (빌드) — local build + branch push

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

Steps

  1. Branch, not main. 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.)
  2. Gate. just check (fmt + clippy -D warnings + tests) must be green before committing. Fix failures; do not commit red. For bridge/runtime changes also install locked bridge dependencies and run just check-bridge; preserve all three embedded bridge assets in filtered build contexts (shared reference).
  3. Build + hot-deploy locally — procedure A in the shared reference (cargo build --release --locked; rm the read-only Cellar file; cp; chmod 755; llmux restart). Autonomous — this is the whole point of build.
  4. Smoke check. /opt/homebrew/bin/llmux status — daemon back up on the new binary, in_flight was 0 before restart. Frontend/runtime changes additionally need the shared reference’s actual native-Codex and Claude-SDK client-tool smokes. Node/npm are required on the daemon only for Claude-through-Codex. Docs-only followups use the shared documentation path without hot-deploying unchanged runtime.
  5. Commit. Conventional, lowercase, no emoji, no AI co-author line (AGENTS.md): git add -A && git commit -m "<type>: <summary>".
  6. Push to the branch (never main): git push -u origin <branch>. On a stale ghs_ token, use the gh auth token fallback (shared reference).
  7. Report branch, commit, and the deployed local version.

Common mistakes

  • cp over the read-only Cellar binary → EACCES. rm -f "$(readlink -f /opt/homebrew/bin/llmux)" first (procedure A).
  • Pushing to main from build — that fires the preview pipeline. Branch only.
  • Committing with just check red, or with an emoji / AI co-author line.
  • A later brew upgrade will overwrite this hot-deployed dev dev binary — expected; re-run build to restore.

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.