orca-sync-fanout

Surveys Orca worktrees behind the default branch and dispatches git-sync to each live agent.

Updated Dec 18, 2025
One-click install
npx skills add https://github.com/l0lxl0lw/dotfiles --skill orca-sync-fanout-l0lxl0lw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: orca-sync-fanout
Source: https://github.com/l0lxl0lw/dotfiles/tree/main/ai/shared/skills/git/orca-sync-fanout
Command: npx skills add https://github.com/l0lxl0lw/dotfiles --skill orca-sync-fanout-l0lxl0lw

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? When a PR lands on the default branch, every other Orca-managed workspace becomes stale, and manually updating each one is tedious and error-prone. This Skill surveys all worktrees for the current repo, reports how many commits behind each one is, and dispatches a /git-sync command into each live agent so it resolves its own conflicts with full context. ## Core Features & Use Cases - Worktree Survey: Runs survey.sh to fetch origin and emit a TSV report of every Orca worktree with its branch, commits behind, live terminal handle, and linked issue. - Safe Dispatch: Waits for each agent to go idle before sending /git-sync, never interrupts work in flight, and never resolves another workspace's conflicts centrally. - Confirmed Fan-out: Always asks the user to confirm the target list before dispatching, and reports workspaces with no live agent along with the command to spawn one. - Use Case: After merging a PR to main, ask which workspaces are behind and fan out the sync so every agent rebases on the updated default branch without you touching each terminal. ## Quick Start Ask the assistant to survey all Orca workspaces for this repo and dispatch git-sync to every agent that is behind the default branch.

Frequently Asked Questions about orca-sync-fanout

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I sync all git worktrees after merging to main?

Run the survey script to list every Orca worktree with its commits-behind count, confirm the target list, then the skill waits for each live agent to go idle and sends it /git-sync. Each agent resolves its own conflicts with its own context.

How do I check which workspaces are behind the default branch?

The survey.sh script fetches origin and outputs a TSV table with path, display name, branch, commits behind, terminal handle, and linked issue for every Orca worktree of the current repo. Workspaces at zero behind are skipped.

Does this work with worktrees that have no running agent?

No dispatch happens for worktrees without a live terminal. The skill reports them and shows the orca terminal create command you can run to spawn an agent there manually.

Why does the skill wait for idle instead of interrupting agents?

Interrupting cuts into work in flight, and a sync is rarely urgent enough to justify that. If the idle wait times out, the agent is reported as skipped (busy) rather than forced.

What are the limitations of dispatching git-sync to other agents?

Dispatch is not completion: each agent still has to run its own sync and may hit conflicts needing its user. The skill never resolves another workspace's conflicts centrally because it lacks that workspace's context.