lanes
Skill0 starsChanged 7 months agoMITView on GitHub
Check progress across all workstream clones. Shows branch, dirty files, last commit, active brief, and backlog for each lane. Works from the main checkout or any clone. Use when asked to "status", "check progress", "what's happening", "show workstreams", or "lane status".
4 other projects use a version of this.
Adopted by
Most recently taken up by
- joris887/exosuittheir own version, first seen Nov 1, 2026
- KrishP147/skillstheir own version, first seen Nov 1, 2026
- grrowl/bb-lanestheir own version, first seen Oct 20, 2026
- thebpandey/lanestheir own version, first seen Oct 2, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- KrishP147/skills★ 37same name
- joris887/exosuit★ 9same name
- thebpandey/lanes★ 9same name
- grrowl/bb-lanes★ 2same name
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.
The file
We split this skill into the rules it gives an agent
9 rules. 0 are common, 7 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
7
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 18
Read-only dashboard showing the state of all workstream clones.
- Very specific: line 66
If DISPATCH-NOTES.md exists, extract cross-lane item titles (lines matching ## Cross-lane:).
- Distinctive: line 105
If BRIEF.md doesn't exist, show "Brief: none"
- Very specific: line 113
If the user invokes /status full or /status --brief:
- Distinctive: line 119
Strictly read-only: Never modify any file, branch, or config.
- Distinctive: line 120
All reads are cross-directory — reads are not sandboxed, no bypass needed.
- Distinctive: line 122
Do not fetch or pull — show local state only.
- Distinctive: line 123
Do not attempt network operations.
- Distinctive: line 124
Keep output compact — one screen or less for the default view.
“Common” is measured: kept by at least 6 in 10 of the 4 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
Status — Workstream Dashboard
Read-only dashboard showing the state of all workstream clones.
Steps
1. Orient
Run in parallel:
basename $(git rev-parse --show-toplevel)— current directory namegit rev-parse --show-toplevel— repo root
Derive the base repo name by stripping any --<suffix> from the directory name.
Set BASE_DIR to the parent of the repo root.
Set MAIN_DIR to BASE_DIR/<base-repo-name>.
This skill works from the main checkout OR any clone. If running from a clone, note it but proceed normally.
2. Discover clones
List all sibling clones:
ls -d BASE_DIR/<base-repo-name>--* 2>/dev/nullExtract the lane name from each suffix. If no clones exist, report "No workstream clones found" and stop.
3. Gather data
For each clone, run ALL of these in parallel (each clone can be a separate parallel Bash call):
echo "=== <lane> ==="
git -C <clone-path> branch --show-current 2>/dev/null || echo "NO BRANCH"
git -C <clone-path> status --porcelain 2>/dev/null
git -C <clone-path> log --oneline -1 2>/dev/null || echo "NO COMMITS"
git -C <clone-path> log main..HEAD --oneline 2>/dev/null | wc -l | tr -d ' 'Also read (reads are not sandboxed):
<clone-path>/BRIEF.md— extract the first# Brief:line and theStatuscheckbox<clone-path>/BACKLOG.md— count###headers (each = one queued item)
For the main checkout:
git -C <MAIN_DIR> status --porcelain 2>/dev/null
git -C <MAIN_DIR> log --oneline -1 2>/dev/null
test -f <MAIN_DIR>/DISPATCH-NOTES.md && echo "has_notes" || echo "no_notes"If DISPATCH-NOTES.md exists, extract cross-lane item titles (lines matching ## Cross-lane:).
4. Detect anomalies
For each clone, check and flag:
- Branch mismatch: current branch doesn't match
feat/<lane>— show "expected feat/<lane>, found<actual>" - Rebase in progress:
git -C <path> statuscontains "rebase in progress" — flag prominently - CLAUDE.md out of sync: compare line count of clone's CLAUDE.md vs main's. If different, flag "CLAUDE.md out of sync — run /dispatch to resync"
- Clone missing: directory doesn't exist — show "NOT FOUND — run /spawn
<lane>"
5. Format output
Print a compact dashboard. Target: fits in one terminal screen.
Status — <base-repo-name> workstreams
═══════════════════════════════════════════════════════
<repo>--<lane> feat/<lane> <N> ahead
Brief: "<title>" [x] Complete | [ ] Not started | [ ] In progress
Backlog: <N> queued
Dirty: <N> files (<file1>, <file2>, ...)
Last: <hash> <message>
─────────────────────────────────────────────────────────
<repo>--<lane> feat/<lane> clean
Brief: none
Backlog: 0 queued
Last: <hash> <message>
─────────────────────────────────────────────────────────
Cross-lane (DISPATCH-NOTES.md): <count> pending
- "<title>" — <lanes involved>
Main (<repo>/) main clean
Last: <hash> <message>
═══════════════════════════════════════════════════════Adapt based on what you find:
- "Dirty" shows up to 4 filenames; beyond that show count only
- "commits ahead" = count from
git log main..HEAD. If 0, show "clean" - If BRIEF.md doesn't exist, show "Brief: none"
- Backlog count = number of
###headers in BACKLOG.md (0 if no file) - Cross-lane section only appears if DISPATCH-NOTES.md exists with items
- Main checkout is always the last row — it's context, not the focus
- Anomaly flags appear inline with the affected clone (e.g., "⚠ Branch mismatch")
Extended mode
If the user invokes /status full or /status --brief:
- Print the full BRIEF.md contents for each clone that has one, indented under the lane section
- Print full BACKLOG.md contents if they exist
Rules
- Strictly read-only. Never modify any file, branch, or config.
- All reads are cross-directory — reads are not sandboxed, no bypass needed.
- Works from the main checkout or any clone.
- Do not fetch or pull — show local state only.
- Do not attempt network operations.
- Keep output compact — one screen or less for the default view.
- Lane discovery is dynamic — scan for
<repo>--*directories, don't hardcode names.
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.

