← ClaudeAtlas

jailbee-usagelisted

Use when running or explaining day-to-day `jailbee` (`jb`) commands against an already-set-up repo — creating/entering/destroying branch containers, the host↔container git bridge (`jailbee git push`/`pull`/`fetch`/`checkout`/`diff`), network modes (`jailbee net strict|loose`), port forwarding (`jailbee port ls`/`to-container`/`to-host`/`rm`), `jailbee dashboard`, snapshots, mounts, `jailbee ide`/`jailbee chrome`, background ops, and reviewing PRs with `jailbee new --pr`. Trigger on "how do I use jailbee", "jailbee new/shell/git/net/port/dashboard", "how do I use gie", "gie new/shell/git/net/port/dashboard" (`gie` was jailbee's pre-1.0 command name, removed in 1.1.0 — users may still say it out of habit), "spin up a container for this branch", "push/pull/merge the container branch", "switch the container to loose/strict", "forward a port into/out of the container", "expose adb inside the container", "review this PR in a container", "luo kontti tälle branchille", "vie/tuo muutokset kontista", "välitä portti kon
VRTFinland/jailbee · ★ 7 · Code & Development · score 68
Install: claude install-skill VRTFinland/jailbee
# Using JailBee day-to-day `jailbee` (short form `jb`) runs many isolated dev environments in parallel on one Linux host. Each environment is an **Incus system container** cloned from a prebuilt "golden image", carrying its own backend, frontend, Docker daemon, IDE, and browser — no port/name/schema collisions between branches. `gie` is the pre-1.0 name of this tool. The `gie` command was **removed in 1.1.0** and no longer exists — always use `jailbee` (or `jb`). If a user types `gie`, tell them the command is now `jailbee`; if a repo still keeps its config in `.gie/`, that directory is still read (deprecated, removed in 2.0.0) and the fix is `git mv .gie .jailbee`. This skill is for **using** an already-configured repo (one that has `.jailbee/config.yaml` and where `jailbee init` + `jailbee base build` have already run). If the repo isn't set up yet, or you need to change `.jailbee/config.yaml`, use the **jailbee-repo-setup** skill instead. Goal: answer almost any "how do I do X with JailBee" question and run the right command without falling back to `jailbee --help` for every step. The full flag-level reference lives in [`references/commands.md`](references/commands.md) — read it when you need an exact flag or an edge case this page doesn't cover. ## Mental model (read this first — it explains every command) Four ideas make the whole tool make sense: 1. **One container per branch.** `jailbee new feat/foo` provisions a container, clones the repo into it, and runs t