skills.rest
ev3rlit
ev3rlitCOMMUNITY
Explore all skills by this author →
GitHub

gsd-reapply-patches

Merge local patch backups into a fresh GSD installation after an upgrade.

Updated Apr 2, 2026
Search Tags:#automation#merge#updates#patches#conflicts#gsd
One-click install
npx skills add https://github.com/ev3rlit/magam-canonical-archive --skill gsd-reapply-patches-ev3rlit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-reapply-patches
Source: https://github.com/ev3rlit/magam-canonical-archive/tree/main/.codex/skills/gsd-reapply-patches
Command: npx skills add https://github.com/ev3rlit/magam-canonical-archive --skill gsd-reapply-patches-ev3rlit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reapply local modifications after updating GSD, ensuring custom changes survive upstream edits and are ready for the next milestone.

Core Features & Use Cases

  • Detects local patches from a stored backup and applies them to the updated GSD installation.
  • Merges user modifications with the new files, preserving intent while respecting upstream edits.
  • Flags conflicts for manual review and resolution when the same region was changed both upstream and locally.

Quick Start

Run the gsd-reapply-patches command after updating GSD to merge your local changes with the new version.

Frequently Asked Questions about gsd-reapply-patches

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

FAQPage Schema
How do I reapply local patches after a GSD update?▼

To reapply local patches after a GSD update, run the gsd-reapply-patches command to merge your stored backup modifications file-by-file into the newly installed version while preserving your custom changes.

How does merging local modifications with upstream edits work?▼

Merging local modifications works by reading backup metadata and comparing local patch backups with newly installed files, automatically applying user changes when safe and flagging conflicts for manual review when upstream edits clash.

What happens when local patches conflict with upstream GSD edits?▼

When local patches conflict with upstream GSD edits, the merge process flags those specific files for manual review and resolution, ensuring that neither set of changes is silently overwritten during the update.

Do I need a backup file to merge local changes into a fresh GSD installation?▼

Yes, you need a backup-meta.json file containing your stored local patch backups to serve as the baseline for comparing and merging your user modifications into the fresh GSD installation.

What is the best way to preserve custom GSD modifications across version upgrades?▼

The best way to preserve custom GSD modifications across upgrades is using an automated patch reapplication tool that reads stored backups, performs a file-by-file merge, and updates the installed manifest to report per-file results.

Why does my GSD update overwrite local file changes instead of merging them?▼

A GSD update overwrites local file changes because the upgrade installs fresh files; you must explicitly reapply patches afterward to read your backups, merge user modifications, and restore custom changes to the new installation.

Related Skills

Explore More Software Engineering Skills→
gesmith0606gesmith0606

gsd-reapply-patches

Reapplies local patches to a new GSD version via three-way merge.

Community
Advanced
assertchrisassertchris
2

custom-conflict-resolution

Resolve Git merge conflicts file by file using a rebase strategy.

Community
Advanced
dobrinz123dobrinz123

gsd-reapply-patches

Reapply local modifications to restored GSD files via three-way merge.

Community
Advanced
TruCol270TruCol270
1

gsd-reapply-patches

Reapply local patches into refreshed GSD installations with three-way or two-way merges.

Community
Advanced