Prevent JSONL conflicts and master commits in Beads workflows.
npx skills add https://github.com/stars-end/agent-skills --skill beads-guard
Please help me install this Agent Skill. Skill: beads-guard Source: https://github.com/stars-end/agent-skills/tree/main/beads-guard Command: npx skills add https://github.com/stars-end/agent-skills --skill beads-guard
Beads Guard provides warning-only guidance to avoid recurring .beads/issues.jsonl conflicts and accidental master commits. It helps ensure you are on a feature branch, up to date with origin/master, and that Beads files are staged with proper Feature-Key commits.
On a Beads-enabled repo, run the guard steps to preflight your Beads work, then proceed with your normal Beads workflow:
High-intent search queries and answers about installing and using this skill.
Beads Guard provides warning-only checks before bd sync, close, or create operations to prevent .beads/issues.jsonl conflicts. It guides you to ensure you're on a feature branch, rebased to origin/master, and have staged Beads files with proper commits, reducing merge conflicts on master.
Before bd pull or bd sync, verify you're on a feature branch, fetch and rebase to origin/master, pull the latest Beads database with bd pull, and stage .beads/issues.jsonl. Beads Guard walks through these preflight steps to ensure clean, conflict-free operations.
Beads Guard checks that commits include Feature-Key trailers with agent and role metadata before bd operations. It guides staging .beads/issues.jsonl and validates standardized commit messaging, ensuring your feature branch stays synchronized and ready for bd pull, close, or create.
Yes. Beads Guard verifies you're on a feature branch before allowing Beads operations, preventing accidental master commits. It provides warning-only guidance and manual workflow steps to keep your work isolated on feature branches.
Your repository must be Beads-enabled. Beads Guard then provides preflight checks on feature branches: it verifies branch context, master synchronization, clean working trees, and stale socket removal without requiring additional dependencies or configuration.
A clean working tree prevents uncommitted changes from conflicting with Beads data during sync or rebase. Beads Guard verifies this state and ensures .beads/issues.jsonl is properly staged before bd pull, close, or create to maintain workflow integrity.
dtbuchholzSynchronize the current Git branch with origin/main via rebase or pull.
otrebuMerge a feature branch into main with conflict handling and push.
MartinoPoloRebase or merge a target branch into the current branch with conflict handling.
tile-aiEnforce Git commit and branch workflows for the TileOPs repository.
