skills.rest
fw-ai
fw-aiOFFICIAL
Explore all skills by this author →
WebsiteGitHub

rebase-upstream-release

Synchronize a GitHub fork with the latest upstream release tag via rebase branch and pull request.

2|1|Updated Oct 21, 2025
Search Tags:#git#release management#github#sync#rebase#fork
One-click install
npx skills add https://github.com/fw-ai/flashinfer --skill rebase-upstream-release
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: rebase-upstream-release
Source: https://github.com/fw-ai/flashinfer/tree/main/.claude/skills/rebase-upstream-release
Command: npx skills add https://github.com/fw-ai/flashinfer --skill rebase-upstream-release

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of synchronizing a forked GitHub repository with the latest release tag of its upstream counterpart, streamlining the update workflow for developers.

Core Features & Use Cases

  • Automated Rebasing: Fetches upstream changes, identifies the latest release tag, and rebases the origin/main branch.
  • PR Creation: Automatically generates a Pull Request to merge the rebased main branch back into the fork's origin/main.
  • Feature Branch Management: Provides a strategy for rebasing existing feature branches onto the newly updated base.
  • Use Case: When the upstream project releases a new version, this Skill can be invoked to update your fork, ensuring your development stays current and minimizing merge conflicts.

Quick Start

Use the rebase-upstream-release skill to sync your fork with the latest upstream release tag.

Frequently Asked Questions about rebase-upstream-release

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

FAQPage Schema
How do I sync a fork with the latest upstream release tag?▼

To sync a fork with the latest upstream release tag, this process fetches upstream changes, creates a rebase branch, and opens a pull request. It automatically rebases origin/main onto the new release tag.

How do I rebase feature branches onto a newly updated upstream release?▼

Rebasing feature branches onto an updated upstream release involves applying existing feature branches onto the newly synchronized base. This strategy ensures your development branches stay current and minimizes potential merge conflicts.

Do I need GitHub CLI to automate syncing my fork with upstream releases?▼

Yes, you need GitHub CLI (gh) and git to automate syncing your fork with upstream releases. The CLI is required to automatically generate the pull request merging the rebased main branch back into your fork.

What is the best way to handle git merge conflicts when rebasing a fork?▼

Handling git merge conflicts when rebasing a fork is managed during the synchronization of the origin/main branch. The process identifies the latest release tag and manages potential conflicts while rebasing feature branches onto the new base.

When should I use an automated rebase to update my GitHub fork?▼

You should use an automated rebase to update your GitHub fork when the upstream project releases a new version. This ensures your development environment stays current with the latest release tag and minimizes manual merge conflicts.

Related Skills

Explore More Software Engineering Skills→
muskie9muskie9

merge-pr

Merge approved GitHub pull requests with branch cleanup and repository synchronization.

Community
Intermediate
idvorkinidvorkin
1

up-to-date

Sync local git repositories with upstream or origin main branches.

Community
Advanced
anajuliabitanajuliabit
6

fork-skill-digest

Compare fork aeon.yml configurations against upstream AEON skill defaults.

Community
Advanced
einja-inceinja-inc
1

conflict-resolver

Resolve git conflicts per file during rebase, merge, stash, or cherry-pick.

Official
Advanced