docs(agents): mark beads/bd tracking as a historical artifact - #237
Conversation
The BEADS INTEGRATION block still presented bd as a live task-tracking
system ("Use bd for ALL task tracking", "Do NOT use external issue
trackers"), but beads was only used during the repository's initial
buildout. The bd database is now stale and may not even open, so this
guidance actively misleads agents into resurrecting a dead workflow.
Replace the ~90-line how-to block with a short note framing `.beads/`
and its database as retained-for-history-only, directing task tracking
to the GitHub issue tracker. Also drop the `bd dolt push` step and the
bd-specific issue-status step from "Landing the Plane", keeping the
still-valid git pull/push/verify flow.
The stale reference to the non-existent docs/QUICKSTART.md is dropped
as part of removing the block.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
📝 WalkthroughWalkthroughAGENTS.md replaces bd-based task tracking guidance with GitHub issue instructions and updates session completion steps to use a git-only synchronization and push workflow. ChangesTask tracking and completion workflow
Estimated code review effort: 1 (Trivial) | ~3 minutes Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 7✅ Passed checks (7 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@AGENTS.md`:
- Around line 399-412: Reconcile the bd retirement guidance in AGENTS.md: update
the historical .beads section at AGENTS.md lines 399-412 to acknowledge that
.beads/hooks/pre-push may still invoke bd, or remove/disable that hook. Also
update the completion workflow at AGENTS.md lines 422-429 to state that git push
origin HEAD can trigger the pre-push hook and account for its behavior.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro Plus
Run ID: 1ce54a4f-b642-443d-8339-ed75faabd390
📒 Files selected for processing (1)
AGENTS.md
CodeRabbit flagged that retaining .beads/hooks/pre-push contradicts the new "do not use bd" guidance, since that script invokes bd when it is on PATH. The script's contents do call bd, but git never runs it: the repo's prepare script installs husky, which sets core.hooksPath to .husky/, so nothing under .beads/hooks/ is ever consulted. Say so explicitly rather than leaving the reader to infer it from the word "retained". Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Summary
AGENTS.mdstill carried a full BEADS INTEGRATION how-to block presenting bd (beads) as the live task-tracking system for this repo — "Use bd for ALL task tracking", "Do NOT use external issue trackers", command recipes, an auto-sync section, etc.That is no longer true. beads was only used during the repository's initial buildout; the
.beads/directory and its bd database are now a historical artifact. The database is stale and may not even open (it currently errors onfailed to initialize schema: pending schema migrations). The old guidance therefore actively misleads AI agents into resurrecting a dead workflow.Changes
.beads/is retained-for-history-only; do not use bd; use the GitHub issue trackerbd dolt pushdocs/QUICKSTART.mdreferenceThe
<!-- BEGIN/END BEADS INTEGRATION -->markers are kept as anchors. They are unrelated to bd's git-hook markers under.beads/hooks/, so this is a plain manual edit — bd tooling does not regenerate this block.Scope / non-changes
AGENTS.mdonly. Not in the npm packagefiles, not the downstreamSKILL.md, so no changeset per thewriting-changesetsskill..beads/files themselves are left in place (still git-tracked) — this PR only stops the docs from telling agents to use them.🤖 Generated with Claude Code
Summary by CodeRabbit