Skip to content
Back to skills

Beads Guard

ASecurity

Safe Beads workflow helper (warning-only). Use before bd sync/close/create to avoid JSONL conflicts. Ensures you are on a feature branch, up to date with origin/master, and stages Beads files cleanly with Feature-Key commits.

  • 18 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added June 1, 2026
toolsbashgitbackend

Security analysis

A100/100

Scanned June 1, 2026

npx -y skills add majiayu000/claude-skill-registry-data --skill beads-guard --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Beads Guard?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Beads Guard
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/majiayu000-beads-guard/badge)](https://www.skillsdirectory.com/skills/majiayu000-beads-guard)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

SKILL.md
---
name: beads-guard
description: |
  Safe Beads workflow helper (warning-only). Use before bd sync/close/create to
  avoid JSONL conflicts. Ensures you are on a feature branch, up to date with
  origin/master, and stages Beads files cleanly with Feature-Key commits.
tags: [beads, dx, guardrail]
---

# Beads Guard

Avoid recurring .beads/issues.jsonl conflicts and master commits.

## How to run (manual steps)

```bash
# 0) Must be on a feature branch (not master)
git status -sb

# 1) Rebase to latest master
git fetch origin master
git rebase origin/master

# 2) Clear stale locks
rm -f .beads/bd.sock* || true

# 3) Pull Beads DB to JSONL
bd pull

# 4) Do your Beads op
#   bd close <id> --reason "..."
#   bd create "..." --type ... --priority ...
#   bd sync

# 5) Stage Beads files
git add .beads/issues.jsonl .beads/deletions.jsonl 2>/dev/null || true

# 6) Commit with Feature-Key trailer (on feature branch)
git commit -m "beads: <summary>\n\nFeature-Key: <id>\nAgent: claude-code\nRole: backend-engineer"

# 7) Push/PR as normal
git push
```

## Notes
- Warning-only flow; no hard blocks.
- If branch is behind master and Beads changed, rebase before committing.
- Keep Beads ops off master to avoid hook warnings.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.