gsd-reapply-patches

Name: gsd-reapply-patches
Availability: InStock
Author: MINT-IA

Merge user patches with updated GSD files using three-way comparison.

Updated Jan 25, 2026

Search Tags:#merge #baseline #conflicts #gsd #patch-management #three-way-merge #local-patches

Ready to run

npx skills add https://github.com/MINT-IA/MINT --skill gsd-reapply-patches-mint-ia

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gsd-reapply-patches
Source: https://github.com/MINT-IA/MINT/tree/main/.claude/skills/gsd-reapply-patches
Command: npx skills add https://github.com/MINT-IA/MINT --skill gsd-reapply-patches-mint-ia

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

After a GSD update wipes and reinstalls files, this process merges the user's previously saved local modifications back into the new version, using a three-way comparison to distinguish user changes from version drift.

Core Features & Use Cases

Detect backed-up patches in gsd-local-patches and locate their directory.
Determine a pristine baseline from git history or a gsd-pristine snapshot to guide reliable merges.
Merge user changes with the updated version, report per-file outcomes, and prompt for review of conflicts.

Quick Start

Run the gsd-update workflow to reapply patches after a GSD update.

Frequently Asked Questions about gsd-reapply-patches

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

FAQPage Schema

How do I restore local modifications after a GSD update overwrites my files?▼

To restore local modifications after a GSD update, merge user patches with the new version using a three-way comparison, which distinguishes your custom changes from version drift.

What is the best way to reapply custom patches when a GSD refresh wipes my configurations?▼

The best way to reapply custom patches is using a strict merging protocol backed by a gsd-local-patches backup and a pristine baseline, ensuring no custom content is silently lost.

How does three-way merge work for resolving local patches against a new GSD baseline?▼

Three-way merge works by comparing your local patches and the updated version against a pristine baseline from git history or a gsd-pristine snapshot, flagging conflicts for manual review.

Do I need a pristine baseline from git history to guide reliable merges of local patches?▼

Yes, a pristine baseline from git history or a gsd-pristine snapshot is needed to guide reliable merges, allowing the process to accurately distinguish your changes from version drift.

What happens to merge conflicts when reapplying local patches after a GSD update?▼

When merge conflicts occur during patch reapplication, the process enforces a strict merging protocol that flags the conflicts for user review and reports per-file outcomes.

Can I use gsd-local-patches to recover custom changes without losing content to version drift?▼

Yes, you can use gsd-local-patches to recover custom changes without losing content, as the process enforces a strict merging protocol to ensure no custom content is silently lost.