How do I install the Bl Record skill?

Run npx skillmds@latest add tomevault-io/bl-record in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Bl Record safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Bl Record?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Bl Record free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Bl Record?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Bl Record by tomevault-io — Agent Skill

Name: Bl Record
Author: tomevault-io

File contents

/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

# 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

Check Prerequisites
- Verify git-branchless is installed
- Verify repository is initialized for branchless
- Check we're in detached HEAD state
Stage Changes (if needed)
- Run git status to check for changes
- If unstaged changes exist, run git add -A to stage all

Record the Commit

If --create-branch is provided:
```
git branchless record -c -m "<message>"
```
Then immediately return to detached HEAD:
```
git checkout --detach
```
Otherwise:
```
git branchless record -m "<message>"
```

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.

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: bl-recorddescription: Record changes as a new commit in git-branchless workflow Use when this capability is needed.---# /bl-record - Git-Branchless Record**Category:** Git WorkflowRecord 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 Instructions1. **Check Prerequisites** - Verify git-branchless is installed - Verify repository is initialized for branchless - Check we're in detached HEAD state2. **Stage Changes (if needed)** - Run `git status` to check for changes - If unstaged changes exist, run `git add -A` to stage all3. **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__.pyRunning: git branchless record -m "feat: add user model"◆ abc1234 (main) initial commit┃● def5678 feat: add user model ← New commitCommit recorded successfully.``````User: /bl-record -m "fix: validate email" --create-branchAgent: Recording changes with branch creation...Staged changes: M src/validators.pyRunning: git branchless record -c -m "fix: validate email"Branch created: fix-validate-emailReturning to detached HEAD...Running: git checkout --detach◆ abc1234 (main) initial commit┃● ghi9012 fix: validate email (fix-validate-email) ← New commit with branchCommit 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.---> Converted and distributed by [TomeVault](https://tomevault.io/claim/jpoutrin) — claim your Tome and manage your conversions.

Frequently asked questions

Bl Record