beads-init

Initialize beads issue tracking with manual staging control over .beads/*.jsonl.

1|Updated Feb 2, 2026
One-click install
npx skills add https://github.com/justin-delano/Claude-Config --skill beads-init
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: beads-init
Source: https://github.com/justin-delano/Claude-Config/tree/main/skills/conditional/beads
Command: npx skills add https://github.com/justin-delano/Claude-Config --skill beads-init

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Beads initialization enables starting beads issue tracking in a project with explicit, manual control over when bead changes enter git history, including options to avoid automatic staging and merge-driver interactions.

Core Features & Use Cases

  • Initialize beads for a new repository with manual staging control over .beads/*.jsonl
  • Support stealth mode to keep beads changes local and invisible to collaborators
  • Provide post-init cleanup steps and guidance for syncing JSONL changes back to git

Quick Start

Run the beads initialization command to prepare the beads workspace for your project.

Frequently Asked Questions about beads-init

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I initialize issue tracking in a git repository without automatic staging?

To initialize issue tracking without automatic staging, run the beads init command to bootstrap the initial database and configuration with deterministic staging control. This sets up the .beads/*.jsonl files while preventing automatic git staging and merge-driver interactions.

What is stealth mode for issue tracking and when do I need it?

Stealth mode for issue tracking keeps your beads changes local and invisible to collaborators. You need it when you want to track issues privately within your repository before explicitly committing those changes to git history.

How do I manually sync JSONL tracking changes back to git history?

To manually sync JSONL tracking changes back to git history, follow the post-init cleanup guidance provided by the initialization command. This gives you explicit control over when .beads/*.jsonl file modifications enter your committed git history.

Does beads initialization require a project prefix?

Yes, beads initialization requires a project prefix to satisfy its init-time configuration requirements. You must provide this prefix during the bootstrap process to properly configure the initial database for your new repository.

Can I use beads issue tracking to avoid triggering git merge drivers?

Yes, you can use beads issue tracking to avoid triggering git merge drivers. The initialization scope includes options to bypass automatic merge-driver interactions, giving you manual control over how tracking changes integrate with your git workflow.