Menu
Set up a private GitHub Dolt repo for personal beads and configure sync for the current project
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Plan and consume execution metadata for bd/beads issues. Use when Codex inspects, triages, claims, tackles, or delegates beads; assign or read suggested agent type, model, reasoning effort, execution mode, and parallel group using the documented execution_* metadata keys.
Initialize or use beads in stealth mode for a project that does not use beads, with issue data stored in a separate syncable repository. Use when the user says "init with stealth", "stealth beads", "use beads without touching this repo", or asks for external BEADS_DIR setup.
Monitor Amp Free quota and handoff before exhaustion. Use when user says quota-watch, check quota, or monitor usage.
Basé sur la classification professionnelle SOC
| name | source-command-setup-beads-sync |
| description | Set up a private GitHub Dolt repo for personal beads and configure sync for the current project |
Use this skill when the user asks to run the migrated source command setup-beads-sync.
Set up personal beads with Dolt sync for the current project.
The user wants personal beads (issue tracking) that are:
Infer the project name from the current git repo:
basename "$(git rev-parse --show-toplevel 2>/dev/null || basename "$PWD")"
Confirm with the user: "Setting up personal beads for . OK?"
gh api user --jq .login
If gh is not authenticated, ask the user for their GitHub username.
mkdir -p ~/.beads-planning/<project-name>
cd ~/.beads-planning/<project-name>
git init
bd init --prefix plan
If ~/.beads-planning/<project-name> already exists, ask the user if they want to reconfigure or abort.
gh repo create beads-planning-<project-name> --private --description "Personal beads for <project-name>" --confirm
cd ~/.beads-planning/<project-name>
bd dolt remote add origin git+ssh://git@github.com/<username>/beads-planning-<project-name>.git
bd dolt push
cd <original-project-dir>
bd config set repos.additional "~/.beads-planning/<project-name>"
bd list # should work (may be empty)
Print instructions the user can run on another machine:
# On your other machine, after cloning <project-name>:
mkdir -p ~/.beads-planning/<project-name>
cd ~/.beads-planning/<project-name>
git init
bd init --prefix plan
bd dolt remote add origin git+ssh://git@github.com/<username>/beads-planning-<project-name>.git
bd bootstrap # or: bd dolt pull
cd <project-dir>
bd config set repos.additional "~/.beads-planning/<project-name>"
Tell the user: "Done. Use bd dolt push / bd dolt pull in ~/.beads-planning/<project-name> to sync."