sync-to-kag

Cherry-pick commits from the main branch to the kag branch.

Updated Feb 2, 2026
One-click install
npx skills add https://github.com/har1101/marp-agent-har1101 --skill sync-to-kag
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sync-to-kag
Source: https://github.com/har1101/marp-agent-har1101/tree/main/.claude/skills/sync-to-kag
Command: npx skills add https://github.com/har1101/marp-agent-har1101 --skill sync-to-kag

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill ensures that critical changes made to the main development branch are consistently applied to the 'kag' branch, maintaining parity between different deployment environments.

Core Features & Use Cases

  • Selective Code Synchronization: Applies specific commits from main to kag using cherry-picking, avoiding full merges.
  • Environment Parity: Keeps the kag environment (e.g., staging) up-to-date with essential features and configurations from main.
  • Use Case: After deploying a new feature to main, use this Skill to apply only that feature's commits to the kag branch for testing before a full production release.

Quick Start

Use the sync-to-kag skill to apply the latest main branch commit to the kag branch.

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 specific commits from main to a staging branch without a full merge?

Cherry-picking specific commits from main to a staging branch avoids full merges by applying individual feature commits. This Skill syncs the main branch to the kag branch, selectively applying commits to maintain environment parity.

What is the best way to maintain code consistency across development and staging environments?

Maintaining code consistency across development and staging environments requires selectively applying application code changes. This Skill syncs the main branch to the kag branch using cherry-picking to ensure essential features and configurations match without merging unrelated history.

Does this git synchronization method exclude documentation and environment-specific settings?

Yes, this synchronization method excludes documentation and environment-specific settings. It only syncs application code and Claude Code configurations to ensure environment parity.

When should I use cherry-pick for branch synchronization instead of a standard git merge?

You should use cherry-pick for branch synchronization when you need to apply specific commits from main to the kag branch for testing before a full production release. It avoids full merges, ensuring only targeted features and configurations are synchronized.

Can I use this to apply a new feature from main to the kag branch for testing?

Yes, you can use this to apply a new feature from main to the kag branch for testing. After deploying a feature to main, this Skill applies only that feature's commits to the kag branch, maintaining separate environment parity.