Best use case
bl-init is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Initialize git-branchless in the current repository from the current branch
Teams using bl-init should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/bl-init/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How bl-init Compares
| Feature / Agent | bl-init | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Initialize git-branchless in the current repository from the current branch
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# /bl-init - Git-Branchless Repository Initialization
**Category:** Git Workflow
Initialize git-branchless in the current repository, using the current branch as the main branch by default. Automatically detaches HEAD so you're ready to start stacking commits.
## Usage
```
/bl-init [options]
```
## Options
| Option | Description |
|--------|-------------|
| (none) | Initialize using current branch as main, then detach HEAD |
| `--main-branch <branch>` | Specify a different branch as main |
| `--no-detach` | Initialize without detaching HEAD |
## Examples
```bash
# Initialize with current branch as main
/bl-init
# Initialize with a specific branch as main
/bl-init --main-branch develop
```
## Execution
This command delegates to the `bl-init-expert` agent:
```
Task(subagent_type="git-workflow:bl-init-expert",
prompt="Initialize git-branchless: <options>")
```
## Execution Instructions
1. **Check Prerequisites**
- Verify this is a git repository
- Check if git-branchless is installed
- Check if already initialized
2. **Determine Main Branch**
- Use current branch if no `--main-branch` specified
- Validate the branch exists
3. **Initialize Git-Branchless**
- Run `git branchless init --main-branch <branch>`
- Configure recommended settings
4. **Detach HEAD** (unless `--no-detach`)
- Run `git checkout --detach`
- This prepares you for the stacked commits workflow
5. **Verify Installation**
- Run `git sl` to confirm working
- Show current state with detached HEAD
6. **Provide Next Steps**
- Explain basic commands (`git sl`, `git sync`, `git submit`)
## Interactive Flow
```
User: /bl-init
Agent: Initializing git-branchless...
Current branch: main
Repository: /path/to/project
Checking prerequisites...
✓ Git repository detected
✓ git-branchless is installed (v0.9.0)
✗ Not yet initialized
Initializing with main branch: main
$ git branchless init --main-branch main
Created config file at .git/branchless/config
Installed hooks at .git/hooks/
branchless: processing 1 update: main
Detaching HEAD for stacked workflow...
$ git checkout --detach
✓ Git-branchless initialized successfully!
Current state:
◆ abc1234 (main) Latest commit message
┃
● abc1234 (HEAD) ← You are here (detached)
Ready to stack commits! Next steps:
1. Use `git record -m "msg"` to create commits
2. Use `git sl` to see your commit stack
3. Use `git sync --pull` to sync with remote
4. Use `git submit` to create/update PRs
```
```
User: /bl-init
(already initialized)
Agent: Checking git-branchless status...
✓ Git-branchless is already initialized in this repository.
Current main branch: main
Config file: .git/branchless/config
Current state:
◆ abc1234 (main) Latest commit
┃
◯ def5678 Your feature commit
To reinitialize with different settings:
1. Remove: rm -rf .git/branchless .git/hooks/post-*
2. Run: /bl-init again
```
```
User: /bl-init --main-branch develop
Agent: Initializing git-branchless with develop as main...
$ git branchless init --main-branch develop
Created config file at .git/branchless/config
Installed hooks at .git/hooks/
branchless: processing 1 update: develop
Detaching HEAD for stacked workflow...
$ git checkout --detach
✓ Git-branchless initialized with main branch: develop
```
```
User: /bl-init --no-detach
Agent: Initializing git-branchless (without detaching)...
$ git branchless init --main-branch main
Created config file at .git/branchless/config
Installed hooks at .git/hooks/
branchless: processing 1 update: main
✓ Git-branchless initialized successfully!
Current state:
◆ abc1234 (main) Latest commit message
Note: HEAD is still attached to main.
When ready to stack commits, run: git checkout --detach
```
## Error Handling
| Error | Resolution |
|-------|------------|
| Not a git repository | Run `git init` first |
| git-branchless not installed | Install with `brew install git-branchless` or `cargo install git-branchless` |
| Branch does not exist | List available branches, suggest correct one |
| Already initialized | Show current config, offer reinit instructions |Related Skills
tmux-init
Set up tmux notification system for Claude Code sessions
zod
Zod schema validation patterns and type inference. Auto-loads when validating schemas, parsing data, validating forms, checking types at runtime, or using z.object/z.string/z.infer in TypeScript.
typescript-import-style
Merge-friendly import formatting (one-per-line, alphabetical). Auto-loads when writing TypeScript/JavaScript imports to minimize merge conflicts in parallel development. Enforces consistent grouping and sorting.
setup-mcp-auth
Configure authentication for an existing FastMCP server
fastmcp
FastMCP TypeScript framework patterns for MCP servers. Auto-loads when building MCP servers, creating tools/resources/prompts, implementing authentication, configuring transports, or working with FastMCP in TypeScript.
add-mcp-tool
Add a new tool to an existing FastMCP server with guided configuration
add-mcp-resource
Add a new resource or resource template to an existing FastMCP server
plan-with-team
Validate plan file ownership
privacy-compliance
GDPR, CCPA, and privacy compliance guidance for data protection. Use when handling personal data, implementing consent management, or ensuring regulatory compliance across jurisdictions.
oauth
OAuth 2.0 and OpenID Connect implementation patterns. Use when implementing authentication, authorization flows, or integrating with OAuth providers like Google, GitHub, or custom identity providers.
mcp-security
Use when securing MCP servers, preventing prompt injection, implementing authorization, validating user input, or building secure multi-agent pipelines. Provides 5-layer defense architecture patterns.
rag-cag-security
Security patterns for RAG and CAG systems with multi-tenant isolation. Use when building retrieval-augmented or cache-augmented generation systems that require tenant isolation, access control, and secure data handling.