bl-record
Record changes as a new commit in git-branchless workflow
What this skill does
# /bl-record - Git-Branchless Record
**Category:** Git Workflow
Record staged/unstaged changes as a new commit using git-branchless. Optionally create a branch for the commit.
## Usage
```
/bl-record [-m <message>] [--create-branch]
```
## Options
| Option | Description |
|--------|-------------|
| `-m <message>` | Commit message (required) |
| `--create-branch` | Create a branch for PR submission (uses `-c` flag) |
## Examples
```bash
# Record with message
/bl-record -m "feat: add user validation"
# Record and create branch for PR
/bl-record -m "fix: handle null input" --create-branch
```
## Execution Instructions
1. **Check Prerequisites**
- Verify git-branchless is installed
- Verify repository is initialized for branchless
- Check we're in detached HEAD state
2. **Stage Changes (if needed)**
- Run `git status` to check for changes
- If unstaged changes exist, run `git add -A` to stage all
3. **Record the Commit**
- If `--create-branch` is provided:
```bash
git branchless record -c -m "<message>"
```
Then immediately return to detached HEAD:
```bash
git checkout --detach
```
- Otherwise:
```bash
git branchless record -m "<message>"
```
4. **Show Result**
- Run `git sl` to display the updated stack
- Confirm the new commit was added
## Flow Examples
```
User: /bl-record -m "feat: add user model"
Agent: Recording changes...
Staged changes:
A src/models/user.py
M src/models/__init__.py
Running: git branchless record -m "feat: add user model"
◆ abc1234 (main) initial commit
┃
● def5678 feat: add user model ← New commit
Commit recorded successfully.
```
```
User: /bl-record -m "fix: validate email" --create-branch
Agent: Recording changes with branch creation...
Staged changes:
M src/validators.py
Running: git branchless record -c -m "fix: validate email"
Branch created: fix-validate-email
Returning to detached HEAD...
Running: git checkout --detach
◆ abc1234 (main) initial commit
┃
● ghi9012 fix: validate email (fix-validate-email) ← New commit with branch
Commit recorded with branch for PR submission.
Use /bl-submit to push the branch.
```
## Error Handling
| Error | Resolution |
|-------|------------|
| No changes to record | Inform user there's nothing to commit |
| Not in detached HEAD | Warn and suggest `git checkout --detach` |
| git-branchless not installed | Provide installation command |
| Repo not initialized | Suggest `/bl-init` |
## Why Detach After Branch Creation?
When using `-c` to create a branch, git-branchless checks out that branch. We immediately detach again to maintain the branchless workflow where you work in detached HEAD and only create branches when submitting PRs.
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.