worktree-data-sync

Synchronize non-git data between Git worktrees with diffing and selective reconciliation.

8|2|Updated Apr 9, 2026

Search Tags:#parallel development #git worktrees #data synchronization #symlinks #datasets #cloud placeholders #diff and apply

Ready to run

npx skills add https://github.com/FuZhiyu/superRA --skill worktree-data-sync

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: worktree-data-sync
Source: https://github.com/FuZhiyu/superRA/tree/main/skills/worktree-data-sync
Command: npx skills add https://github.com/FuZhiyu/superRA --skill worktree-data-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pytest, and includes scripts (resource) components.

What problem does it solve?

This Skill prevents missing or inconsistent datasets, outputs, caches, and external data links when work moves between Git worktrees.

Core Features & Use Cases

Seed Data: Materialize missing managed files in a destination worktree without overwriting existing content.
Diff and Reconcile: Compare source and destination data, then apply selected changes by overwriting or creating renamed copies.
Safe Worktree Handling: Discover managed paths from Git ignore rules and external symlinks, preserve cloud placeholders, validate endpoints, and reject unsafe path traversal.
Use Case: When parallel research branches produce outputs in separate worktrees, compare their generated files and copy selected results into the integration worktree.

Quick Start

Use the worktree-data-sync skill to seed all managed non-git data from the current worktree into the specified destination worktree.

Frequently Asked Questions about worktree-data-sync

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

FAQPage Schema

How do I synchronize non-git data like datasets and caches between git worktrees?▼

To synchronize non-git data between git worktrees, you can use a diff and apply approach that compares source and destination worktrees, then selectively overwrites or seeds missing managed files like datasets and caches without altering existing content.

What is the best way to keep symlinks and external data links consistent across parallel development branches?▼

Keeping symlinks and external data links consistent across parallel development branches requires discovering managed paths from Git ignore rules and external symlinks, then safely reconciling them to prevent missing links in destination worktrees.

How do I copy generated outputs from one worktree to an integration worktree without overwriting existing files?▼

You can copy generated outputs by using a seeding function that materializes missing managed files in the destination worktree from the source, ensuring existing content is preserved while selected results are applied.

Does git worktree data synchronization handle cloud placeholders and unsafe path traversal?▼

Git worktree data synchronization can handle cloud placeholders by preserving them during the sync process, and it rejects unsafe path traversal to ensure secure filesystem access across source and destination directories.

Can I compare and reconcile renamed files between separate git worktrees?▼

Yes, you can compare source and destination data to identify differences and apply selected changes by overwriting or creating renamed copies, allowing for accurate reconciliation of renamed files between worktrees.

Do I need Python 3 and pytest to run worktree data synchronization scripts?▼

You need Python 3, Git worktree metadata, and filesystem access to run the bundled discovery and synchronization scripts, while pytest is an optional dependency specifically for running the included tests.