sync

Rebases Git feature branches onto origin/main and reports conflicts without resolving them.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/KosmoCHE/claude-plugins --skill sync-kosmoche
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sync
Source: https://github.com/KosmoCHE/claude-plugins/tree/main/git-command/skills/sync
Command: npx skills add https://github.com/KosmoCHE/claude-plugins --skill sync-kosmoche

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Skill helps developers keep their feature branches up to date with the latest changes by rebasing onto main, avoiding merge commits and preserving a linear history.

Core Features & Use Cases

  • Rebase onto origin/main to maintain a clean, linear project history.
  • Detect conflicts and report them without auto-resolving, letting you handle resolutions.
  • Warn about unsafe pushes and advise safe alternatives for shared branches.

Quick Start

Rebase the current feature branch onto origin/main and verify a clean, linear history.

Frequently Asked Questions about sync

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

FAQPage Schema
How do I rebase a feature branch onto main to maintain a linear git history?

To maintain a linear git history, rebase your feature branch onto origin/main. This replays your commits onto the latest main, avoiding merge commits and keeping the project history clean and linear.

What happens when git conflicts occur during a rebase onto main?

When git conflicts occur during a rebase, the process reports the conflicting files without auto-resolving them. This ensures deterministic guidance and lets you handle the conflict resolutions manually.

What is the best way to sync a feature branch with the latest main branch?

The best way to sync a feature branch with main is by rebasing onto origin/main. This synchronizes your branch with the latest changes while enforcing a clean, linear project history without merge commits.

Is it safe to force push a rebased feature branch to a shared remote?

Force pushing a rebased feature branch to a shared remote is unsafe. The process warns about unsafe pushes and advises safe alternatives to prevent overwriting teammates' commits on shared branches.

When should I avoid rebasing my feature branch in version control?

You should avoid rebasing your feature branch if it is a shared branch that others have based work on. Rebasing rewrites commit history, which can cause issues for collaborators, so shared-branch cautions apply.