skills.rest
wangrenzhu-ola
wangrenzhu-olaCOMMUNITY
Explore all skills by this author →
GitHub

compound-sync

Sync GaleHarnessCLI skills with upstream changes and re-inject HKTMemory patches.

2|1|Updated Apr 17, 2026
Search Tags:#automation#worktree#sync#patch#upstream#gh-renames#hktmemory
One-click install
npx skills add https://github.com/wangrenzhu-ola/GaleHarnessCodingCLI --skill compound-sync
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: compound-sync
Source: https://github.com/wangrenzhu-ola/GaleHarnessCodingCLI/tree/main/plugins/galeharness-cli/skills/compound-sync
Command: npx skills add https://github.com/wangrenzhu-ola/GaleHarnessCodingCLI --skill compound-sync

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Sync GaleHarnessCLI skills with upstream changes from the reference repo, apply gh: renames, and re-inject HKTMemory patches to keep your fork aligned.

Core Features & Use Cases

  • Batch-based upstream syncing: initialize, process, and complete patches per upstream commit.
  • Per-commit patch workflow: generate an adapted patch for each commit and manage isolated worktrees.
  • Safety and consistency: re-apply gh: naming expectations and ensure patches are validated before merging.

Quick Start

From the repository root, run the upstream-sync CLI to initialize a batch, then step through one commit at a time to generate an adapted patch and open a PR.

Frequently Asked Questions about compound-sync

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

FAQPage Schema
How do I sync a fork with upstream changes and re-apply local patches?▼

To sync a fork with upstream changes, initialize a batch from the repository root, process commits individually to generate adapted patches, and validate them before merging to keep your fork aligned while re-injecting custom patches.

What do I need to set up before starting an upstream sync workflow?▼

Before starting an upstream sync workflow, you need a local clone containing the .upstream-ref and .upstream-repo files to track the reference state, and the process utilizes isolated .context worktrees for applying patches.

How does the per-commit patch workflow handle isolated changes during syncing?▼

The per-commit patch workflow handles isolated changes by generating an adapted patch for each individual upstream commit and managing them within isolated worktrees, ensuring patches are validated before merging and updating the .upstream-ref.

Can I automate renaming gh: prefixes during the upstream sync process?▼

Yes, you can automate renaming gh: prefixes during the upstream sync process, as the workflow automatically re-applies gh: naming expectations to ensure consistency and safety when aligning your fork with the upstream repository.

What is the best way to manage batch-based upstream updates for a local clone?▼

The best way to manage batch-based upstream updates is to initialize a batch, step through one commit at a time to generate an adapted patch, open a PR for review, and update the .upstream-ref after successful merges.

Related Skills

Explore More Software Engineering Skills→
VMAFxVMAFx
3

refresh-ffmpeg-patches

Rebase an ffmpeg patch series onto upstream changes and regenerate clean patches.

Official
Advanced
popoffvgpopoffvg

work-pr

Create pull requests for Git repositories with unpushed commits.

Community
Intermediate
Doyajin174Doyajin174
1

using-git-worktrees

Create isolated Git worktrees for parallel feature development.

Community
Advanced
HardyLiu6HardyLiu6

using-git-worktrees

Create isolated git worktrees for feature branch development.

Community
Advanced