Bd to Br Migration
Migrate docs from bd (beads) to br (beads_rust). Use when updating AGENTS.md, converting bd commands, "bd sync" → "br sync --flush-only", or beads migration.
Install
npx skills add ratacat/claude-skills --skill bd-to-br-migrationgit clone --depth 1 https://github.com/ratacat/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/skills/bd-to-br-migration ~/.claude/skills/bd-to-br-migrationPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# bd → br Migration > **Core Philosophy:** One behavioral change, mechanical transforms. The ONLY difference is git handling—everything else is find-replace. ## Why This Matters Incomplete migrations leave broken docs. Agents follow stale `bd sync` instructions, expect auto-commit, and lose work. This skill ensures **complete, verified migrations**. --- ## THE EXACT PROMPT — Single File Migration ``` Migrate this file from bd (beads) to br (beads_rust). Apply transforms IN THIS ORDER (order matters): 1. Section headers: "bd (beads)" → "br (beads_rust)" 2. Add non-invasive note after beads section header 3. Commands: `bd X` → `br X` for ready/list/show/create/update/close/dep/stats 4. Sync command: `bd sync` → `br sync --flush-only` 5. Add git steps after EVERY sync: git add .beads/ git commit -m "sync beads" 6. Issue IDs: bd-### → br-### in thread_ids, subjects, reasons, commits 7. Links: beads_viewer → beads_rust (if present) Remove completely: - Daemon references - Auto-commit assumptions - Hook installation mentions - RPC mode Keep unchanged: - SQLite/WAL cautions - bv integration - Priority system (P0-P4) VERIFY after editing: grep -c '`bd ' file.md # Must be 0 grep -c 'bd sync' file.md # Must be 0 grep -c 'br sync --flush-only' file.md # Must be > 0 ``` ### Why This Prompt Works - **Ordered transforms**: Dependencies exist (sync must change before adding git steps) - **Explicit removals**: Daemon/RPC don't exist in br—leaving them confuses agents
Details
- Skill name
bd-to-br-migration- Repository
- ratacat/claude-skills
- Path
skills/bd-to-br-migration/SKILL.md- Repo updated
- 11 February 2026
FAQ
What does the Bd to Br Migration skill do?
Migrate docs from bd (beads) to br (beads_rust). Use when updating AGENTS.md, converting bd commands, "bd sync" → "br sync --flush-only", or beads migration.
How do I install the Bd to Br Migration skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add ratacat/claude-skills --skill bd-to-br-migration. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Bd to Br Migration popular?
It lives in ratacat/claude-skills, which has 59 GitHub stars and 10 forks.
Related skills
Skill Creator
59ratacat/claude-skills
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Codex's capabilities with specialized knowledge, workflows, or tool integrations.
Skill Installer
59ratacat/claude-skills
Install Codex skills into $CODEX_HOME/skills from a curated list or a GitHub repo path. Use when a user asks to list installable skills, install a curated skill, or install a skill from another repo (including private repos).
Agent Browser
59ratacat/claude-skills
Browser automation using Vercel's agent-browser CLI. Use when you need to interact with web pages, fill forms, take screenshots, or scrape data. Alternative to Playwright MCP - uses Bash commands with ref-based element selection. Triggers on "browse website", "fill form", "click button", "take screenshot", "scrape page", "web automation".
Compound Docs
59ratacat/claude-skills
Capture solved problems as categorized documentation with YAML frontmatter for fast lookup
Ankane Readme Writer
59ratacat/claude-skills
Use this agent when you need to create or update README files following the Ankane-style template for Ruby gems. This includes writing concise documentation with imperative voice, keeping sentences under 15 words, organizing sections in the standard order (Installation, Quick Start, Usage, etc.), and ensuring proper formatting with single-purpose code fences and minimal prose. Examples: <example>Context: User is creating documentation for a new Ruby gem. user: "I need to write a README for my new search gem called 'turbo-search'" assistant: "I'll use the ankane-readme-writer agent to create a
Every Style Editor
59ratacat/claude-skills
This skill should be used when reviewing or editing copy to ensure adherence to Every's style guide. It provides a systematic line-by-line review process for grammar, punctuation, mechanics, and style guide compliance.
Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.