Foremerge
naw103/foremerge
Coordinate parallel coding agents with Foremerge's local Git-compatible CLI and MCP server.
Official skill for beadsrust (br), a local-first, dependency-aware issue tracker for AI agents.
Install Br
$ npx skills add Dicklesworthstone/beads_rust --skill br -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Dicklesworthstone/beads_rust br --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Dicklesworthstone/beads_rust.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/br .claude/skills/br && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "br" agent skill from https://github.com/Dicklesworthstone/beads_rust/tree/main/.claude/skills/br into .claude/skills/br/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "br", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Dicklesworthstone/beads_rust/tree/main/.claude/skills/brType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Dicklesworthstone/beads_rust --skill br -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Dicklesworthstone/beads_rust br --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Dicklesworthstone/beads_rust.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/br .agents/skills/br && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "br" agent skill from https://github.com/Dicklesworthstone/beads_rust/tree/main/.claude/skills/br into .agents/skills/br/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "br", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Dicklesworthstone/beads_rust --skill br -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Dicklesworthstone/beads_rust br --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Dicklesworthstone/beads_rust.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/br .cursor/skills/br && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "br" agent skill from https://github.com/Dicklesworthstone/beads_rust/tree/main/.claude/skills/br into .cursor/skills/br/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "br", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Dicklesworthstone/beads_rust.git --path .claude/skills/br--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Dicklesworthstone/beads_rust --skill br -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Dicklesworthstone/beads_rust br --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Dicklesworthstone/beads_rust.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/br .gemini/skills/br && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "br" agent skill from https://github.com/Dicklesworthstone/beads_rust/tree/main/.claude/skills/br into .gemini/skills/br/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "br", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Dicklesworthstone/beads_rust brInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Dicklesworthstone/beads_rust --skill br -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Dicklesworthstone/beads_rust.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/br .github/skills/br && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "br" agent skill from https://github.com/Dicklesworthstone/beads_rust/tree/main/.claude/skills/br into .github/skills/br/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "br", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Dicklesworthstone/beads_rust --skill br -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Dicklesworthstone/beads_rust br --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Dicklesworthstone/beads_rust.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/br .opencode/skills/br && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "br" agent skill from https://github.com/Dicklesworthstone/beads_rust/tree/main/.claude/skills/br into .opencode/skills/br/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "br", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
br- GitHub stars
- 1.1k
- Token cost
- ~2.7k tokens
- SKILL.md length
- 404 words
- Files
- 5 (incl. references)
- Skills in repo
- 2
- Repo updated
- First seen
- Licence
- MIT
At a glance
Official skill for beadsrust (br), a local-first, dependency-aware issue tracker for AI agents.
- Creating issues
- SKILL.md covers Critical Rules for Agents, Quick Workflow, Essential Commands and Priority Scale, plus 11 more sections
- Calls git and jq
- Triaging backlogs
What it does
Br is an agent skill from Dicklesworthstone/beads_rust. Official skill for beadsrust (br), a local-first, dependency-aware issue tracker for AI agents. Use when creating issues, triaging backlogs, managing dependencies, finding ready work, updating status, or syncing to git via JSONL.
Its SKILL.md is about 2.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `references/COMMANDS.md`, `references/CONFIG.md` and `references/INTEGRATION.md`).
It sits in Development, covering Issue triage and Git workflow. It works with Rust, Git and SQLite. The repository describes itself as: Fast Rust port of Steve Yegge's beads: local-first, non-invasive issue tracker storing tasks in SQLite with JSONL export for git collaboration. The licence is MIT.
When your agent uses it
- Creating issues
- Triaging backlogs
- Managing dependencies
- Finding ready work
Example prompts
- “/br”
Requirements
- Python 3
What it can do on your machine
Read from SKILL.md and the folder at commit 3cc83ba. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
gitjq
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Br loads about 2.7k tokens when it runs, and up to ~6k if it reads all its reference files. Until then it costs about 59 tokens; SKILL.md has 404 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Dicklesworthstone/beads_rust at commit 3cc83ba, republished under its MIT licence (© Dicklesworthstone). 404 words, ~2,705 tokens.
Download SKILL.mdSave it as
.claude/skills/br/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- br
- description
- Official skill for beads_rust (`br`), a local-first, dependency-aware issue tracker for AI agents. Use when creating issues, triaging backlogs, managing dependencies, finding ready work, updating status, or syncing to git via JSONL.
- license
- MIT
- domain
- project-management
- role
- specialist
- scope
- operations
- output-format
- commands
- triggers
- br, beads, beads_rust, issue tracker, issue triage, backlog, dependencies, ready work
- metadata.author
- Dicklesworthstone
- metadata.version
- 1.0.0
<!-- TOC: Critical Rules | Quick Workflow | Essential Commands | Dependencies | Sync | bv Integration | Agent Mail | Troubleshooting | References -->br -- Beads Rust Issue Tracker (Official Skill)
Non-invasive: br NEVER runs git commands. Sync and commit are YOUR responsibility.
Critical Rules for Agents
| Rule | Why |
|---|---|
Binary is br | NEVER bd (that is the old Go version) |
ALWAYS use --json | Structured output for parsing; --format toon for reduced tokens |
NEVER run bare bv | Blocks session in interactive TUI mode |
| Sync is EXPLICIT | br sync --flush-only exports DB to JSONL only |
| Git is YOUR job | br only touches .beads/ -- you must git add .beads/ && git commit |
| No cycles allowed | br dep cycles must return empty |
| Resolve actor at runtime | Use ACTOR="${BR_ACTOR:-assistant}" and pass --actor "$ACTOR" |
Quick Workflow
ACTOR="${BR_ACTOR:-assistant}"
# 1. Find work
br ready --json
# 2. Claim it
br update --actor "$ACTOR" <id> --status in_progress
# 3. Do work...
# 4. Complete
br close --actor "$ACTOR" <id> --reason "Implemented X"
# 5. Sync to git (EXPLICIT!)
br sync --flush-only
git add .beads/ && git commit -m "feat: X (<id>)"Essential Commands
Issue Lifecycle
ACTOR="${BR_ACTOR:-assistant}"
br init # Initialize .beads/ workspace
br create --actor "$ACTOR" "Title" -p 1 -t task # Create issue (priority 0-4)
br q --actor "$ACTOR" "Quick note" # Quick capture (ID only output)
br show <id> --json # Show issue details
br update --actor "$ACTOR" <id> --status in_progress # Update status
br update --actor "$ACTOR" <id> --priority 0 # Change priority
br close --actor "$ACTOR" <id> --reason "Done" # Close with reason
br close --actor "$ACTOR" <id1> <id2> --reason "..." # Close multiple at once
br reopen --actor "$ACTOR" <id> # Reopen closed issueCreate Options
br create --actor "$ACTOR" "Title" \
--priority 1 \ # 0-4 scale (0=critical, 4=backlog)
--type task \ # task, bug, feature, epic, question, docs
--assignee "user@..." \ # Optional assignee
--labels backend,auth \ # Comma-separated labels
--description "..." # Detailed descriptionUpdate Options
br update --actor "$ACTOR" <id> \
--title "New title" \
--priority 0 \
--status in_progress \ # open, in_progress, closed
--assignee "new@..." \
--add-label reliability \
--parent <parent-id> \
--claim # Shorthand for claim-and-startBulk update (batch triage):
br update --actor "$ACTOR" <id1> <id2> <id3> --priority 2 --add-label triage-reviewed --jsonQuerying (always use --json for agents)
br ready --json # Actionable work (no blockers)
br list --json # All issues
br list --status open --sort priority --json # Filter and sort
br list --priority 0-1 --json # Filter by priority range
br list --assignee alice --json # Filter by assignee
br blocked --json # Show blocked issues
br search "keyword" --json # Full-text search
br show <id> --json # Issue details with dependencies
br stale --days 30 --json # Stale issues
br count --by status --json # Count with groupingDependencies
br dep add <child> <parent> # child depends on parent
br dep add <id> <depends-on> --type blocks # Explicit block type
br dep remove <child> <parent> # Remove dependency
br dep list <id> --json # List dependencies for issue
br dep tree <id> --json # Show dependency tree
br dep cycles --json # Find circular deps (MUST be empty!)Critical: br dep cycles must return empty. Circular dependencies break the dependency graph and make br ready unreliable.
Labels
br label add <id> backend auth # Add multiple labels
br label remove <id> urgent # Remove label
br label list <id> # List issue's labels
br label list-all # All labels in projectComments
ACTOR="${BR_ACTOR:-assistant}"
br comments add --actor "$ACTOR" <id> --message "Triage note" --json
br comments list <id> --jsonSync (EXPLICIT -- never automatic)
br sync --flush-only # Export DB to JSONL (before git commit)
br sync --import-only # Import JSONL to DB (after git pull)
br sync --status # Check sync statusWorkflow after making changes:
br sync --flush-only
git add .beads/ && git commit -m "Update issues"Workflow after pulling:
git pull
br sync --import-onlySystem and Diagnostics
br doctor # Full diagnostics
br stats --json # Project statistics
br config list # Show all configuration
br config get id.prefix # Get specific value
br config set defaults.priority=1 # Set value
br where # Show workspace location
br version # Show version
br upgrade # Self-update (if enabled)
br lint --json # Lint issues for problemsPriority Scale
| Priority | Meaning | Use numbers, not words |
|---|---|---|
| 0 | Critical | Immediate action required |
| 1 | High | Important, do soon |
| 2 | Medium (default) | Normal priority |
| 3 | Low | When time permits |
| 4 | Backlog | Future consideration |
Issue Types
task, bug, feature, epic, question, docs
Output Formats
| Flag | Use case |
|---|---|
--json | Default for agents -- full structured data |
--format toon | Token-optimized alternative for context-window-sensitive agents |
| (no flag) | Human-readable terminal output with colors |
bv Integration
CRITICAL: Never run bare bv -- it launches interactive TUI and blocks.
# Always use --robot-* flags:
bv --robot-next # Single top pick + claim command
bv --robot-triage # Full triage with recommendations
bv --robot-plan # Parallel execution tracks
bv --robot-insights | jq '.Cycles' # Check graph health (must be empty)
bv --robot-priority # Priority misalignment detection
bv --robot-alerts # Stale issues, blocking cascadesShow full SKILL.md (167 more words)Show less
Agent Mail Coordination
Use bead ID as thread_id for multi-agent coordination:
| Concept | Value |
|---|---|
Mail thread_id | bd-### (the issue ID) |
| Mail subject | [bd-###] ... |
File reservation reason | bd-### |
| Commit messages | Include bd-### for traceability |
# 1. Reserve files for bead
file_reservation_paths(..., reason="bd-123")
# 2. Announce work in thread
send_message(..., thread_id="bd-123", subject="[bd-123] Starting...")
# 3. Do work...
# 4. Close bead and release
br close bd-123 --reason "Completed"
release_file_reservations(...)Session Ending Pattern
Before ending any work session:
git pull --rebase
br sync --flush-only
git add .beads/ && git commit -m "Update issues"
git push
git status # MUST show "up to date with origin"Standard Agent Workflow (Full)
ACTOR="${BR_ACTOR:-assistant}"
# 1. Verify workspace
br where
br ready --json
br blocked --json
br list --status open --sort priority --json
# 2. Pick highest-priority ready work
br show <id> --json
# 3. Claim it
br update --actor "$ACTOR" <id> --status in_progress --claim
# 4. Do work...
# 5. Close with evidence
br close --actor "$ACTOR" <id> --reason "Implemented X in commit abc123"
# 6. Check queue impact
br ready --json
br blocked --json
# 7. Sync to git
br sync --flush-only
git add .beads/ && git commit -m "feat: X (<id>)"
git pushTriage Decision Matrix
Classify each issue into exactly one category:
| Classification | Action |
|---|---|
implemented | Close with evidence (commit/PR/file/behavior) |
out-of-scope | Close with explicit boundary reason |
needs-clarification | Comment with specific unanswered questions |
actionable | Keep open, correct status/priority/labels/deps |
During large triage efforts, checkpoint every few updates:
br ready --json
br blocked --jsonAnti-Patterns
- Running
br syncwithout--flush-onlyor--import-only - Forgetting sync before git commit
- Creating circular dependencies
- Running bare
bv(blocks session) - Assuming auto-commit behavior (br NEVER auto-commits)
- Inventing evidence for closure -- if unsure, comment instead
- Modifying unrelated issues during triage
- Adding speculative dependencies
Storage Layout
.beads/
beads.db # SQLite database (primary storage)
beads.db-shm # SQLite shared memory (WAL mode)
beads.db-wal # SQLite write-ahead log
issues.jsonl # JSONL export (for git)
config.yaml # Project configuration
metadata.json # Workspace metadataTroubleshooting
br doctor # Full diagnostics
br dep cycles # Must be empty
br config list # Check settings
which br # Verify br is installed"Database locked": Check for other br processes with pgrep -f "br ".
Worktree error ('main' is already checked out):
git branch beads-sync main
br config set sync.branch beads-syncVerbose debugging:
br -v list # Verbose
br -vv list # Debug
RUST_LOG=debug br list # Detailed trace logsReferences
| Topic | File |
|---|---|
| Command cookbook | references/COMMANDS.md |
| Configuration details | references/CONFIG.md |
| Troubleshooting guide | references/TROUBLESHOOTING.md |
| Multi-agent integration | references/INTEGRATION.md |
© Dicklesworthstone, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 4 other files (references) in .claude/skills/br of Dicklesworthstone/beads_rust.
- SKILL.md
- references/COMMANDS.md
- references/CONFIG.md
- references/INTEGRATION.md
- references/TROUBLESHOOTING.md
Open the folder on GitHubat commit 3cc83ba
Compare with similar skills
Br next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Br this skillDicklesworthstone/beads_rust | 1.1k | — | ~2.7k | Automated safety check: Pass | MIT | |
| Foremergenaw103/foremerge | 538 | — | ~2.4k | Automated safety check: Pass | Apache-2.0 | |
| Worktrunk Release Workflowmax-sixty/worktrunk | 9.1k | — | ~6.9k | Automated safety check: Pass | Custom licence | |
| TiXL Ticket Processortixl3d/tixl | 5.1k | — | ~2.6k | Automated safety check: Pass | MIT | |
| SkillhoneTencent/SkillHone | 168 | — | ~3.4k | Automated safety check: Pass | Custom licence | |
| Guarded Git Commit and Pushjerrywu001/cc-sessions-viewer | 395 | — | ~603 | Automated safety check: Notes | MIT |
Similar skills
Worktrunk Release Workflow
max-sixty/worktrunk
Walks a maintainer through cutting a Worktrunk release: sync the release branch, pass two test gates, review the changes, then publish.
TiXL Ticket Processor
tixl3d/tixl
Works through the In progress column of the TiXL road-map board unattended, turning simple tickets into git stashes and writing plans for the rest under .agentic/Plans.
Skillhone
Tencent/SkillHone
Local Issue, pull-request, and Wiki workbench for agent skills.
Guarded Git Commit and Push
jerrywu001/cc-sessions-viewer
Commits and pushes only on an explicit request, pulling first, running the project's CI checks locally, and stopping cold on any conflict or failure.
Stax Dev
cesarferreira/stax
Development harness for the stax Rust CLI project. An agent skill from cesarferreira/stax.
More from Dicklesworthstone/beads_rust
Bd To Br Migration
Dicklesworthstone/beads_rust
Migrate docs from bd (beads) to br (beadsrust). An agent skill from Dicklesworthstone/beads_rust.
Related
Categories
Questions about Br
What does Br do?
Official skill for beadsrust (br), a local-first, dependency-aware issue tracker for AI agents. Br is an agent skill from Dicklesworthstone/beads_rust. Official skill for beadsrust (br), a local-first, dependency-aware issue tracker for AI agents.
When should I use Br?
Br fits situations like: creating issues; triaging backlogs; managing dependencies; finding ready work.
How do I install Br in Claude Code?
Run `npx skills add Dicklesworthstone/beads_rust --skill br -a claude-code`. Or copy the skill folder (.claude/skills/br in Dicklesworthstone/beads_rust) into .claude/skills/br in your project. Claude Code loads it when a task matches its description.
How do I install Br in Codex?
Run `npx skills add Dicklesworthstone/beads_rust --skill br -a codex`. Or copy the skill folder (.claude/skills/br in Dicklesworthstone/beads_rust) into .agents/skills/br in your project. Codex loads it when a task matches its description.
Can I use Br in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Dicklesworthstone/beads_rust --skill br -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/br, .gemini/skills/br, .github/skills/br and .opencode/skills/br in your project.
What does Br need to run?
Going by SKILL.md and its folder, Br needs the command-line tools its instructions call (git and jq). Our summary lists: Python 3.
Does Br access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Br safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Br use?
Br is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Br use?
About 2.7k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.3k tokens, read only when the agent opens those files.
What are the alternatives to Br?
Skills that share tags, products or a category with Br: Foremerge (naw103/foremerge, 538 stars), Worktrunk Release Workflow (max-sixty/worktrunk, 9.1k stars), TiXL Ticket Processor (tixl3d/tixl, 5.1k stars) and Skillhone (Tencent/SkillHone, 168 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Br?
Dicklesworthstone (a GitHub user) maintains it in Dicklesworthstone/beads_rust, which has 1,120 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 9, 2026.
Source: Dicklesworthstone/beads_rust on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.