sync-to-kag

Cherry-pick commits from the main repository into the kag repository.

108|19|Updated Jan 24, 2026
One-click install
npx skills add https://github.com/minorun365/marp-agent --skill sync-to-kag-minorun365
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sync-to-kag
Source: https://github.com/minorun365/marp-agent/tree/main/.agents/skills/sync-to-kag
Command: npx skills add https://github.com/minorun365/marp-agent --skill sync-to-kag-minorun365

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill ensures changes from the main repository are reliably applied to the kag repository without merging, using cherry-pick to maintain separate histories.

Core Features & Use Cases

  • Selective synchronization: cherry-pick commits from the main repository into kag to keep histories in sync without merging.
  • Cross-repo coordination: works with independently managed repos that use an upstream remote for kag.
  • Guardrails & error handling: detects conflicts and guides resolution to preserve integrity of both repos.

Quick Start

Identify the target commit in the main repository, then cherry-pick it into the kag repository and push the changes.

Frequently Asked Questions about sync-to-kag

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

FAQPage Schema
How do I sync commits between git repositories without merging their histories?

To sync commits between git repositories without merging, use cherry-pick to selectively apply specific commits from the main repository into the target repository. This maintains separate histories while keeping both repos in sync.

What is the best way to cherry-pick specific commits across multiple independently maintained repositories?

The best way to cherry-pick across multiple repositories is to configure an upstream remote for the target repository, identify the intended target commits, and execute the cherry-pick to apply only those changes without merging branch histories.

How do I handle git cherry-pick conflicts when synchronizing changes to another repository?

When handling cherry-pick conflicts during repository synchronization, you must detect the conflicts and manually guide the resolution to preserve the integrity of both repositories before pushing the updated history.

Do I need to set up an upstream remote to apply changes from a main repository to another git repo?

Yes, you need to set up an upstream remote for the target repository to fetch and cherry-pick commits from the main repository, ensuring correct cross-repo coordination and allowing the updated history to be pushed.

Can I use cherry-pick for cross-repo synchronization instead of merging branches?

Yes, cherry-pick is designed for cross-repo synchronization to avoid merges entirely. It selects and applies only the intended commits from the main repository, keeping independently maintained repos updated without merging histories.