chore: bd init + Claude Code project assets #5
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "chore/bd-init-setup"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Brings the bd (beads) issue-tracker setup and project-level Claude Code orchestration assets into
develop. None of the three open feature PRs (#2 #3 #4) can have a clean diff until these files exist ondevelop, because they were all branched off a local commit that adds them.After this merges, the feature PR diffs will collapse to only their actual feature changes — no rebase needed on those branches.
Commits
d728fd07bd init: initialize beads issue tracking— generated bybd init; adds.beads/(config, hooks, metadata), the.beads-credential-key/*.db/.dolt/entries in.gitignore, and a bd Issue Tracker section inAGENTS.md.6ddc8639chore: complete bd init setup and add .claude orchestration assets— the rest of the per-project Claude Code config that was still uncommitted locally:.claude/(agents, hooks, rules, skills, settings), the Grimmory orchestration section appended toAGENTS.md,.claude/.upgrades/added to.gitignore, anddolt.auto-push: falsein.beads/config.yaml.Notes
CLAUDE.mdis a symlink toAGENTS.md, so the Beads + orchestration content is consumed by both Claude Code (which reads CLAUDE.md) and other agent runtimes (which read AGENTS.md)..claude/.upgrades/is Claude Code's local upgrade cache and stays untracked.dolt.auto-push: falseskips the dolt-sidegit pushafter eachbdwrite; can be re-enabled withbd config set dolt.auto-push trueonce the Forgejo remote is confirmed writable.Test plan
.beads/,.claude/,AGENTS.md,.gitignore.