git-sync

Synchronize local Git branches with upstream and resolve merge conflicts.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/zcawood-mie/agentz --skill git-sync-zcawood-mie
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-sync
Source: https://github.com/zcawood-mie/agentz/tree/main/skills/git-sync
Command: npx skills add https://github.com/zcawood-mie/agentz --skill git-sync-zcawood-mie

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Synchronizes local branches with upstream and resolves merge conflicts.

Core Features & Use Cases

  • Syncing workflow guidance for pulling with rebase, merging when necessary, and avoiding interactive rebase.
  • Post-sync verification steps to ensure no conflict markers remain and the codebase builds.
  • Use Case: A feature branch that has fallen behind the main branch can be brought up-to-date with minimal disruption and a clean history.

Quick Start

Use git pull --rebase origin main to update your feature branch.

Frequently Asked Questions about git-sync

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

FAQPage Schema
How do I sync a local feature branch with upstream and resolve merge conflicts?

To sync a local feature branch with upstream and resolve merge conflicts, use a non-interactive strategy like git pull --rebase. This updates your branch and remediates conflicts while maintaining a clean history.

What is the best way to update a feature branch that has fallen behind the main branch?

The best way to update a feature branch fallen behind main is pulling with rebase to bring it up-to-date with minimal disruption. Merge when necessary, while avoiding interactive rebase workflows.

Why does TypeScript compilation fail after a Git rebase?

TypeScript compilation can fail after a Git rebase if merge conflicts are not fully remediated. Post-sync verification checks for leftover conflict markers and ensures the codebase builds properly.

Can I use an interactive rebase to sync branches and resolve conflicts?

No, you should not use an interactive rebase to sync branches. The workflow enforces a non-interactive sync strategy using git pull --rebase or merge to automate conflict remediation and validation.

What post-sync validation steps are needed to ensure no merge conflict markers remain?

Post-sync validation steps to ensure no merge conflict markers remain involve checking the codebase for leftover markers, verifying TypeScript compilation passes, and running tests to validate the sync.