bl-sync

bl-sync is a skill for Claude Code from jpoutrin/product-forge. It costs 21 tokens per session (972 once invoked), scanned A, original, MIT.

A Git-branchless workflow helper that synchronizes a stack of related commits with the main branch. Git-branchless is a Git workflow for building and managing several dependent commits, often used for stacked pull requests.

In plain words
What is it for?
Use it to sync a commit stack with local or remote main, pull the latest changes, handle merge conflicts, and clean up after a merge.
Why use it?
It reduces the manual work of fetching updates, rebasing dependent commits, and cleaning up after a pull request is merged.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter.

Part of the git-workflow plugin — 11 skills, 8 agents shipped together

Good fit Use it to sync a commit stack with local or remote main, pull the latest changes, handle merge conflicts, and clean up after a merge.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jpoutrin/product-forge/bl-sync
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add jpoutrin/product-forge --skill bl-sync
Clone the repo
git clone --depth 1 https://github.com/jpoutrin/product-forge

Made for: Claude Code.

Or install git-workflow, the plugin that ships this one along with the rest of its 11 skills, 8 agents.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for bl-sync

README.md
[![agentmods](https://agentmods.dev/badge/skills/jpoutrin/product-forge/bl-sync/github.svg)](https://agentmods.dev/skills/jpoutrin/product-forge/bl-sync)
Your own site
<a href="https://agentmods.dev/skills/jpoutrin/product-forge/bl-sync"><img src="https://agentmods.dev/badge/skills/jpoutrin/product-forge/bl-sync/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for bl-sync

Your own site · 80×15
<a href="https://agentmods.dev/skills/jpoutrin/product-forge/bl-sync"><img src="https://agentmods.dev/badge/skills/jpoutrin/product-forge/bl-sync.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 21 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 972 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00021 $0.00972
Opus 5.5 $0.00008 $0.00389
Sonnet 5.5 $0.00004 $0.00194
Haiku 4.5 $0.00002 $0.00097

Measured 1mo ago against content hash 1137347dbfa0, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

bl-sync scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/git-workflow/skills/bl-sync/SKILL.md · 177 lines

How it starts

The opening of the file, as written. The whole thing — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/bl-sync - Git-Branchless Stack Sync

Category: Git Workflow

Sync your commit stack with the main branch. Fetches remote changes, rebases your stack, and handles post-merge cleanup.

Usage

/bl-sync [options]

Options

Option Description
(none) Sync with local main branch
--pull Fetch remote + sync with updated main
--after-merge Clean up after a PR was merged

Examples

# Sync with local main
/bl-sync

# Fetch and sync (most common)
/bl-sync --pull

# After your PR was merged on GitHub
/bl-sync --after-merge

Execution

This command delegates to the bl-sync-expert agent:

Task(subagent_type="git-workflow:bl-sync-expert",
     prompt="Execute sync: <options>")

Execution Instructions

  1. Verify Prerequisites

    • Check git-branchless is installed
    • Check working directory is clean
  2. Show Current State

    • Run git sl to display the stack
    • Show divergence from main if any
  3. Execute Sync

    • For basic sync: git sync
    • For pull + sync: git sync --pull
    • For after-merge: git pull origin main then git move
  4. Handle Conflicts

    • Show conflicting files
    • Guide through resolution
    • Continue with git rebase --continue
  5. Remind About PRs

    • If branches exist, suggest git submit to update PRs
  6. Confirm Result

    • Show final state with git sl

Interactive Flow

User: /bl-sync --pull

Agent: Fetching and syncing with main...

Fetching from origin...
remote: Counting objects: 5, done.

Current stack:
◆ old-main (main) old commit
┃
◯ abc123 feat: add User class
┃
● def456 feat: add validation

Syncing onto updated main...
[1/2] feat: add User class - ✓
[2/2] feat: add validation - ✓

◆ new-main (main) teammate's feature  ← Updated
┃
◯ xyz789 feat: add User class
┃
● uvw012 feat: add validation

Stack synced! 2 commits rebased onto updated main.

Note: Run `git submit` to update your PRs.
User: /bl-sync --after-merge

Agent: Cleaning up after PR merge...

Pulling latest main...
Already up to date with merge commit.

Current state:
◆ merge123 (main) Merge pull request #1
┃
✕ old-abc feat: add User class (merged)
┃
◯ def456 feat: add validation  ← Needs moving
┃
● ghi789 feat: add repository

Moving remaining commits onto merge...
git move -s def456 -d merge123

◆ merge123 (main) Merge pull request #1
┃
◯ new-def feat: add validation  ← Moved
┃
● new-ghi feat: add repository

Cleanup complete!

Next steps:
1. Recreate branch: git switch -c pr/validation
2. Push to remote: git submit -c @
3. Update PR base branch on GitHub

Read the full file on GitHub · 177 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago First seen · 177 lines · 21 tokens per session scan A 1137347dbfa0

Subscribe to this mod's changes

bl-sync is a skill published in the GitHub repository jpoutrin/product-forge (16 stars, last pushed 7mo ago), licensed MIT. It adds 21 tokens to every session and 972 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.