Synchronize an ops fork with upstream ApexYard releases via merge or rebase.
npx skills add https://github.com/me2resh/apexyard --skill update-me2resh
Please help me install this Agent Skill. Skill: update Source: https://github.com/me2resh/apexyard/tree/main/.claude/skills/update Command: npx skills add https://github.com/me2resh/apexyard --skill update-me2resh
This Skill removes the error-prone manual process of updating a fork by automating fetch, preview, conflict handling, and the per-version migration chain required to stay compatible with upstream framework changes.
upstream and origin, previews the commit delta, and then syncs via either merge (default) or rebase while refusing risky states (dirty tree, wrong branch, missing upstream remote).--skip-migrations mode for files-only sync, and offers a controlled “update chain” when jumping multiple releases..gitignore, writes the .apexyard-fork marker, and updates project-config.json.Run the update as a merge-based sync to pull in the latest tagged upstream release and its required migrations: /update
High-intent search queries and answers about installing and using this skill.
A safe fork sync validates git state, previews upstream commit deltas, and refuses risky operations on dirty trees or missing remotes, automating fetch and branch-based merge or rebase to protect local changes.
Conflict resolution during upstream merge is handled by automating branch-based merges or rebases with operator-controlled choices across per-version migration chains, ensuring deterministic framework update outcomes.
When jumping multiple upstream releases, the update process walks per-version migration chains sequentially, applying operator-controlled choices to ensure fork compatibility with required framework changes at each tagged release.
Yes, you can skip migrations and sync only files by using the `--skip-migrations` mode, which bypasses release-aware migration handling and performs a files-only sync with the upstream repository.
Git rebase is fully supported as an alternative to the default merge strategy for syncing framework forks, allowing operators to choose their preferred method while still enforcing safety gates like validating git state and resolving upstream refs.
Your fork update fails because safety gates refuse risky states like a dirty tree, wrong branch, or missing `upstream` remote, ensuring deterministic framework updates are only applied in a clean git state.
idvorkinSync local git repositories with upstream or origin main branches.
nirholasAutomate ClawRouter releases with version sync, builds, tests, and GitHub releases.
pko89403Run release-readiness and deployment checks with a rule-based checklist.
chiptoe-svgDetect and merge upstream updates for git branch-distributed skills.