FrostyyTiger

Laneboard — Git skill for Claude Code

Git community

Shows all Claude Code sessions on one machine on a single page, grouped into lanes (one worktree, one branch, one plan) with their PRs, checks and rate-limit spend.

How to install Laneboard

This entry records only its repository, not the path inside it, so there is no exact command to give. Open FrostyyTiger/laneboard and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Laneboard does

Shows all Claude Code sessions on one machine on a single page, grouped into lanes (one worktree, one branch, one plan) with their PRs, checks and rate-limit spend.

Alternatives in Git

Triage Open Pull Requests — Review, label, and act on all open PRs for a repository using parallel review agents 10.8k ★
Codebase To Course — by Zara Zhang - A Claude Code skill that turns any codebase into a beautiful, interactive single-page HTML cou 2.1k ★
Cmt — When user uses /cmt slash command, commit current git changes using fast mode by default, or strict mode when 301 ★

README

laneboard

One page that shows every Claude Code session on a machine, grouped into **lanes** — a lane being a git worktree with one branch, one plan and one piece of work — plus the two acts that make a lane, `launch` and `retire`.

One Node 24 process, no build step, six dependencies. It binds `127.0.0.1` only: laneboard has no login and can type into terminals, so anything that exposes it (a tailnet, a reverse proxy) has to do the authentication.

With a `fleet` block, several of these boards sit behind one **hub**: a separate laneboard in `mode: "hub"` that shows and drives every builder through signed, audited requests. Without one, nothing changes. See **[docs/fleet.md](docs/fleet.md)**.

View	Answers
Map `#/map`	The home view. What is all this running on, and where is the trouble? A live constellation of your sites, rooms, services, builders and lanes, with what depends on what, which lanes touch the same files and which conflict. Overlays for status, CI, cost, context and age; `\` splits it with a dense lane table. Fed by a topology file, snapshots other machines push, and HTTP probes; laneboard reaches out to nothing else.
Board `#/board`	What is each lane doing, and which one wants me? One data block per lane and session: builder, state, stage, PR and checks, context, 5 h spend, age. Sorted by the most urgent thing inside.
Inbox `#/inbox`	What is waiting for me? Pending approvals, lanes that need you, lanes ready for review, paused and stuck lanes, with keys to approve, deny, release and pause.
Packages `#/packages`	What state is each package in? Its CI on main, untested commits, the lanes and PRs touching it, predicted conflicts and plan status.
Morning `#/morning`	Over a window (12 h / tonight / 24 h / 7 d): what needs a human (`danger` first), what finished (with its PR), review waits, stuck incidents, what it cost.
Runs `#/runs`	Is tonight's unattended loop getting anywhere