bl-init
Initialize git-branchless in the current repository from the current branch
What this skill does
# /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 in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.