A helper for creating an isolated Git worktree for a Beads task. Beads is a task-tracking workflow, and a worktree is a separate checkout where you can work without changing the main checkout.

Use it when starting a Beads task that needs its own checkout, such as parallel development or work that should remain isolated.

It keeps parallel or long-running work separated from the main branch and follows the repository's required sibling-folder convention. It also checks the starting branch and working tree before setup.

How kikin81/nubecita configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to kikin81/nubecita. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/kikin81/nubecita/main/.claude/skills/bd-worktree/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/kikin81/nubecita

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/kikin81/nubecita/bd-worktree/github.svg)](https://agentmods.dev/skills/kikin81/nubecita/bd-worktree)

Your own site

<a href="https://agentmods.dev/skills/kikin81/nubecita/bd-worktree"><img src="https://agentmods.dev/badge/skills/kikin81/nubecita/bd-worktree/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/kikin81/nubecita/bd-worktree"><img src="https://agentmods.dev/badge/skills/kikin81/nubecita/bd-worktree.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 63 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,007 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00063	$0.01007
Opus 5	$0.00032	$0.00504
Sonnet 5	$0.00013	$0.00201
Haiku 4.5	$0.00006	$0.00101

Measured 9d ago against content hash a8e55bd7fb84, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

bd-worktree scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/bd-worktree/SKILL.md · 67 lines

How it starts

The opening of the file, as written. The whole thing — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Project-local skill for spinning up a git worktree against a beads ticket. Companion to bd-workflow (standard non-worktree branch/commit/PR ceremony).

Announce at start: "I'm using the bd-worktree skill to set up an isolated worktree for <bd-id>."

When to use

Parallel work — keep main repo on main while another task progresses isolated
Dispatching a subagent that needs a clean checkout (see superpowers:dispatching-parallel-agents)
Long-running work whose state should survive repo-wide branch switches

If none apply, prefer bd-workflow (single checkout, branch in place).

Path convention

Always create the worktree as a sibling at ../nubecita-<bd-id>. Anything under the repo root (.worktrees/, worktrees/) is forbidden — spotless + gradle walk the filesystem ignoring .gitignore and any tree under the repo root breaks the build. bd worktree create defaults to ./<name> (inside the repo), so always pass an explicit ../nubecita-<bd-id> path. Feature-name slugs drift; bd ids are stable.

Pre-flight

git branch --show-current — must be main (or a base the user explicitly specifies).
git diff --quiet && git diff --cached --quiet — tracked tree clean. Untracked OK.
bd show <id> --json | jq -r '.[0] | "\(.status) \(.issue_type)"' — must exist, status != "closed", type != "epic". Refuse epics and point at a child.
ls -d ../nubecita-<bd-id> 2>/dev/null — must NOT exist. If it does, reuse (cd ../nubecita-<bd-id>) or bd worktree remove first.

Create

# Branch name per bd-workflow slug rules: lowercase, non-alphanum → -, cap 50.
TYPE=feat   # or chore/fix/docs/refactor/test/perf/ci/build/style — derive from bd issue_type
BRANCH="$TYPE/<bd-id>-$SLUG"

bd worktree create ../nubecita-<bd-id> --branch="$BRANCH"
bd update <bd-id> --claim

Order doesn't matter — bd 1.0.4 shares the canonical dolt server from the worktree via git common-dir discovery, so bd update --claim from either the main repo or the new worktree lands in the same DB. Verify with cd ../nubecita-<bd-id> && bd dolt status — the PID and data dir match the main checkout's bd dolt status.

Read the full file on GitHub · 67 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

9d ago First seen · 67 lines · 63 tokens per session scan A a8e55bd7fb84

Subscribe to this mod's changes

bd-worktree is a skill published in the GitHub repository kikin81/nubecita (5 stars, last pushed yesterday), licensed MIT. It adds 63 tokens to every session and 1,007 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Git and workflow Project management

mcore-split-pr

Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.

NVIDIA/skills · 25 tokens

shiplog

Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.

aeonfun/aeon · 46 tokens

llxprt-issue-workflow

Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the stepfun-37 smoke test), open code review (ocr), PR…

vybestack/llxprt-code · 87 tokens

nubecita: Skill for Claude Code