wrkx-pull

Fast-forward wrkx.json managed repositories to their baseBranch tip.

Updated Apr 8, 2026

Search Tags:#automation #git #multi-repo #workspaces #pull #basebranch

Ready to run

npx skills add https://github.com/ClankerGuru/opsx --skill wrkx-pull

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: wrkx-pull
Source: https://github.com/ClankerGuru/opsx/tree/main/cli/src/main/resources/content/skills/wrkx-pull
Command: npx skills add https://github.com/ClankerGuru/opsx --skill wrkx-pull

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Syncs multiple workspace repositories to the tip of their baseBranch without merging, preventing messy histories and ensuring consistency across a project workspace.

Core Features & Use Cases

Bulk fast-forward: Update all repos to the remote baseBranch in a single operation.
Per-repo control: Target a single repo with a focused pull when needed.
Guardrails: Report dirty or diverged repos and abort non-fast-forward merges per repo to preserve history.

Quick Start

Execute the aggregate pull to fast-forward all workspace repositories to their configured baseBranch, skipping dirty ones.

Frequently Asked Questions about wrkx-pull

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

FAQPage Schema

How do I fast-forward multiple git repositories to their base branch at once?▼

Fast-forward multiple git repositories to their base branch by executing an aggregate pull operation. This uses git fetch and git merge --ff-only across all wrkx.json managed workspaces, updating every repo to the remote tip in a single action without creating merge commits.

What happens to dirty worktrees when pulling multiple workspace repositories?▼

Dirty worktrees are reported and skipped during the multi-repo pull process. The sync operation identifies repositories with uncommitted changes, aborts the fast-forward merge for those specific repos, and provides a report of which workspaces need attention before they can be updated.

Can I pull updates for a single repository instead of all workspaces?▼

Yes, you can target a single repository for a focused pull instead of updating all workspaces. This per-repo control allows you to fast-forward one specific workspace to its declared baseBranch tip using the same git fetch and merge --ff-only logic without touching the others.

What is a git fast-only merge and why use it for multi-repo workspaces?▼

A fast-forward only merge updates your branch pointer directly to the remote tip without creating a merge commit. Using git merge --ff-only for multi-repo workspaces prevents messy histories and ensures consistency by aborting any updates that would require a true merge due to diverged branches.

Do I need cloned repositories and a wrkx.json file to sync multiple workspaces?▼

Yes, you need locally cloned repositories, a declared baseBranch, a reachable remote, and a wrkx.json configuration file. These prerequisites allow the tool to identify managed repos, execute git fetch operations, and apply the fast-forward merges across the workspace.

Why does my multi-repo pull abort when branches have diverged?▼

Multi-repo pulls abort for diverged branches to preserve your commit history and prevent unwanted merge commits. The tool reports these diverged repositories so you can manually resolve the conflicts, ensuring the workspace sync only succeeds when a clean fast-forward to the baseBranch is possible.