bro

name

bro

description

Coordinate work across sibling LSP repos (css-lsp, epub-lsp, sqlite-lsp, go-template-lsp). Spawns parallel agents to do work in each repo, then commits and pushes each. Use when: (1) user says /bro, (2) user says "update our LSPs", (3) user wants to bump the toba/lsp library version across sibling repos, (4) user wants to apply changes, fixes, or issue work across all sibling LSP repos simultaneously.

Bro — Sibling LSP Coordinator

Spawn one agent per sibling LSP repo to perform work in parallel, then commit and push each.

Sibling Repos

All live under ../ relative to toba/lsp:

Repo	Path
css-lsp	../css-lsp
epub-lsp	../epub-lsp
sqlite-lsp	../sqlite-lsp
go-template-lsp	../go-template-lsp

Workflow

1. Determine the work to do. If the user specifies work (e.g. "work on open issues", "bump deps"), use that. Default work (when the user gives no specific instructions): update each repo to use the latest released version of github.com/toba/lsp by running go get github.com/toba/lsp@latest && go mod tidy and updating any code that uses changed APIs.

2. Get the latest toba/lsp version by running git -C /Users/jason/Developer/toba/lsp describe --tags --abbrev=0 — this is needed even for non-default work since agents often need to know the current library version.

3. Spawn one Agent per repo (all in parallel, run in background). Each agent prompt must include:

   • The absolute path to the repo
   • The specific work to perform
   • The current toba/lsp version tag
   • Instruction to read the repo's CLAUDE.md first
   • Instruction to check jig todo list --json --full for relevant issues and update their status
   • Instruction to run golangci-lint run --fix and go test ./... after code changes
   • Instruction to use /commit --push when done (this handles changelog, release tag, and push)

4. Wait for all agents to complete, then summarize results to the user.

Agent Prompt Template

Use this as the base prompt for each agent, filling in {REPO}, {REPO_PATH}, {WORK}, and {LSP_VERSION}:

You are working in the {REPO} repository at {REPO_PATH}.

First, read CLAUDE.md in the repo root for project conventions.

Current toba/lsp library version: {LSP_VERSION}

## Task

{WORK}

## Process

1. Check for relevant issues: `jig todo list --json --full`
   - If issues relate to your work, update status to in-progress: `jig todo update <id> -s in-progress`
   - Track progress by checking off todo items as you complete them

2. Do the work:
   - Read and understand existing code before making changes
   - Make the necessary code changes
   - Run `golangci-lint run --fix` after changes
   - Run `go test ./...` to verify

3. Update issues:
   - Check off completed items in issue bodies
   - Mark issues as completed when all items are done
   - Add a Summary of Changes section

4. Commit and push using the /commit skill with --push flag.
   Run: invoke the Skill tool with skill="commit" args="--push"

Important Notes

• Always spawn agents in parallel (all in one message with run_in_background: true)
• Each agent works independently in its own repo — no coordination needed between them
• If a repo has no relevant work or issues, the agent should report that and skip
• The /commit skill handles changelog updates and release tagging automatically