catchup-upstream

Fetch, classify, and cherry-pick upstream commits into a fork.

2|Updated Dec 20, 2020
One-click install
npx skills add https://github.com/buvis/home --skill catchup-upstream
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: catchup-upstream
Source: https://github.com/buvis/home/tree/main/.claude/skills/catchup-upstream
Command: npx skills add https://github.com/buvis/home --skill catchup-upstream

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sync a fork with upstream by reviewing new commits and selectively applying relevant changes.

Core Features & Use Cases

  • Identify and fetch new upstream commits and compare them with forked changes.
  • Classify commits as take, skip, or ask, and present a summary before applying.
  • Apply approved commits via cherry-pick, handling conflicts with guided manual adaptation if needed.

Quick Start

Provide the upstream owner/repo or URL and let the tool fetch, review, and selectively apply new commits.

Frequently Asked Questions about catchup-upstream

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

FAQPage Schema
How do I selectively cherry-pick upstream commits to my git fork?

To selectively cherry-pick upstream commits to your git fork, this Skill fetches new upstream changes, classifies them as take or skip, and applies only the approved patches via git cherry-pick. It handles conflicts with guided manual adaptation.

How does incremental upstream review work across multiple fork branches?

Incremental upstream review works across multiple fork branches by using a stored cursor to track the last reviewed commit. This allows you to fetch, diff, and classify only new upstream changes for each branch during subsequent syncs.

What is the best way to sync a fork with upstream without merging everything?

The best way to sync a fork without merging everything is to review a diff of new upstream commits and selectively apply relevant patches. You classify changes as take, skip, or ask, then cherry-pick approved commits individually.

Do I need to manually resolve conflicts when cherry-picking upstream changes?

You may need to manually resolve conflicts when cherry-picking upstream changes. When the cherry-pick encounters a conflict, the Skill provides guided manual adaptation steps to help you integrate the patch correctly into your fork.

Can I review upstream changes before applying them to my fork?

Yes, you can review upstream changes before applying them to your fork. The Skill presents a summary of new commits classified as take, skip, or ask, allowing you to approve changes before any git cherry-pick operations are executed.