update

Sync an ApexYard fork with upstream via merge or rebase and migrations.

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/AAbdulghany/fms --skill update-aabdulghany
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: update
Source: https://github.com/AAbdulghany/fms/tree/main/.claude/skills/update
Command: npx skills add https://github.com/AAbdulghany/fms --skill update-aabdulghany

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps a fork aligned with upstream by providing an automated workflow for previews, merges, rebases, and per-version migrations, reducing manual maintenance and risk.

Core Features & Use Cases

  • Preview upstream changes and determine the best integration strategy (merge or rebase) on a dedicated sync branch.
  • Automatically apply per-version migrations and handle conflicts with guided resolution.
  • Support for --from-dev pre-release syncs and dry-run previews, plus advisory config migrations for split-portfolio layouts.

Quick Start

Run the /update command to synchronize your ApexYard fork with upstream, selecting merge or rebase and optionally applying per-version migrations.

Frequently Asked Questions about update

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

FAQPage Schema
How do I sync a fork with upstream and handle per-version migrations?

To sync a fork with upstream, you can preview changes, apply merges or rebases on a dedicated branch, and execute per-version migrations with guided conflict resolution.

What is the best way to preview upstream changes before merging a fork?

The best way to preview upstream changes is using a dry-run on a dedicated sync branch, allowing you to determine the optimal integration strategy before executing a merge or rebase.

Can I sync pre-release updates from a dev branch using rebase?

Yes, you can sync pre-release updates from a dev branch using the --from-dev flag, which supports both merge and rebase execution along with branch creation.

How do I resolve merge conflicts when synchronizing portfolio layouts?

When synchronizing multipart portfolio layouts, you can resolve merge conflicts through guided conflict resolution integrated into the automated upstream sync workflow.

Does this fork sync tool support advisory config migrations for split layouts?

Yes, this fork sync tool supports advisory config migrations specifically designed for split-portfolio layouts across v1 and v2 portfolio structures.

When should I choose rebase over merge for upstream synchronization?

You should choose rebase over merge when you want to maintain a linear project history, using the plan preview to evaluate the best integration strategy for your upstream sync.