skills.rest
tecnologia-ibtech
tecnologia-ibtechCOMMUNITY
Explore all skills by this author →
GitHub

geo-repo-sync

Synchronize geo-claude changes into geo-codex with dry-run previews and conflict detection.

Updated Mar 29, 2026
Search Tags:#repository#sync#conflicts#dry-run#geo-codex#geo-claude
One-click install
npx skills add https://github.com/tecnologia-ibtech/geo-codex --skill geo-repo-sync
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: geo-repo-sync
Source: https://github.com/tecnologia-ibtech/geo-codex/tree/main/skills/geo-repo-sync
Command: npx skills add https://github.com/tecnologia-ibtech/geo-codex --skill geo-repo-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This repo-local skill enables safe, reversible synchronization of changes from geo-claude into geo-codex, helping teams refresh or preview incoming updates without risking unintended overrides.

Core Features & Use Cases

  • Dry-run previews to show exactly what would change without applying anything
  • Conflict-aware updates with stop-on-conflicts to prevent data loss
  • Path-limited syncing to focus on specific parts of the repository when needed

Quick Start

Run the dry-run wrapper to preview changes before applying them.

Frequently Asked Questions about geo-repo-sync

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

FAQPage Schema
How do I safely synchronize changes between two repositories without overwriting files?▼

Repository synchronization with this skill requires a dry-run preview before applying any changes, using stop-on-conflicts to prevent data loss and sync-rules.json at the repo root to govern mappings and exclusions.

How do I preview repository changes before applying them to production?▼

Dry-run previews show exactly what would change during repository synchronization without applying anything, allowing teams to safely review incoming updates before committing them to the target repository.

Can I limit repository synchronization to specific paths instead of syncing everything?▼

Yes, path-limited syncing focuses on specific parts of the repository when needed. You can target specific paths for selective updates while using sync-rules.json to govern mappings and exclusions at the repo root.

Does repository sync stop automatically when it detects file conflicts?▼

Yes, conflict-aware updates use stop-on-conflicts to prevent data loss. The synchronization process halts automatically when conflicts are detected, ensuring no unintended overrides occur during the claude-to-codex sync.

What configuration is needed to set up selective path updates for repository sync?▼

Selective path updates require a sync-rules.json file at the repo root to govern mappings and exclusions. This configuration controls which paths are synced and enforces claude-to-codex as the sole synchronization direction.

Why does my repository synchronization only work in one direction?▼

Repository synchronization enforces claude-to-codex as the sole direction to ensure safe, reversible updates. This unidirectional constraint prevents circular syncing and maintains a clear source-to-target update hierarchy.

Related Skills

Explore More Software Engineering Skills→
dazzajidazzaji
9

warp-mesh-peer

Attach Claude Code and Codex to Warp panes via the tmux mesh.

Community
Intermediate
Nairon-AINairon-AI
7

flux-sync

Trigger plan-sync to update downstream task specs after code drift.

Official
Advanced
jduttonjdutton
3

vv-validate-dev-loop

Automate code validation loops with vibe-validate commands and YAML error extraction.

Community
Advanced
spyqsspyqs

update-nanoclaw

Synchronize a customized NanoClaw fork with upstream updates via merge, cherry-pick, or rebase.

Community
Advanced