bd-to-br-migration

Migrate bd documentation references to br across files with automated verification.

Updated Jul 15, 2013
One-click install
npx skills add https://github.com/oysteinkrog/dotfiles --skill bd-to-br-migration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bd-to-br-migration
Source: https://github.com/oysteinkrog/dotfiles/tree/main/.claude/skills/bd-to-br-migration
Command: npx skills add https://github.com/oysteinkrog/dotfiles --skill bd-to-br-migration

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a structured, automated path to migrate documentation references from bd (beads) to br (beads_rust), preventing drift and ensuring consistency across projects.

Core Features & Use Cases

  • Automates header changes, command renames, and issue ID rewrites according to the defined transform rules.
  • Includes built-in verification to detect remaining bd references and ensure br commands are present.
  • Supports both single-file migrations (e.g., AGENTS.md) and bulk migrations across many files with batch planning.

Quick Start

Start by locating all impacted files with the included discovery script, then apply the transforms to one file or a batch and finally run the verification script to confirm completion.

Frequently Asked Questions about bd-to-br-migration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate documentation references from bd to br across multiple projects?

You can migrate documentation references from bd to br using an automated skill that enforces exact transforms for header changes, command renames, and sync adjustments. It supports single-file and bulk batch migrations to ensure consistency.

What is the best way to ensure consistency when renaming commands in markdown files?

Ensuring consistency when renaming commands is best achieved with an automated migration tool featuring built-in verification. It detects remaining outdated references and confirms the new commands are correctly present across all files.

Can I automate header changes and issue ID rewrites for a batch of files?

Yes, you can automate header changes and issue ID rewrites for a batch of files. The migration process includes batch planning to apply defined transform rules consistently across many files simultaneously.

How do I verify that all bd references have been replaced after a migration?

To verify all bd references are replaced, run an automated verification script after applying the transforms. This script detects any remaining old references and ensures the new br commands are successfully present.

Does the bd to br migration support single files like AGENTS.md?

Yes, the bd to br migration supports single-file migrations like AGENTS.md alongside bulk batches. You can apply exact transforms to individual files or plan a batch migration across multiple projects.