beads-init
Initializing, bootstrapping and completing beads
bd init does a lot in one go: it creates .beads/, installs git hooks, writes AGENTS.md,
CLAUDE.md and editor integrations, and commits all of it itself. There is no flag to skip
the commit (checked against bd 1.3.1), so the way to get the settings this author wants into
that commit is to apply them right after init and amend. bd bootstrap is the counterpart
for a clone that already tracks .beads/: it clones the Dolt database from the git origin,
but it does not restore the per-clone wiring, and it may edit a tracked file on the way:
ignore patterns it appends are kept and committed, anything else it changes is reverted.
A repo can also sit between the two: .beads/ and its database exist, but some of what init
would have written is missing (--skip-agents, --skip-hooks, an init older than the skill
installer, or this skill's settings never applied). bd init refuses to run there, and the
pieces it would have written are installed one at a time with bd setup <tool>,
bd hooks install and bd config set, none of which commit.
This skill has three modes. Decide which one applies before running anything, from three facts gathered at the repo root: