gsd-reapply-patches

Merge backed-up patches into updated GSD versions with three-way or two-way fallback.

8|Updated Apr 9, 2026

Search Tags:#git #patches #conflicts #merges #baselines #gsd #patch-management

Ready to run

npx skills add https://github.com/D0NMEGA/donnyclaude --skill gsd-reapply-patches-d0nmega

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gsd-reapply-patches
Source: https://github.com/D0NMEGA/donnyclaude/tree/main/packages/skills/gsd-reapply-patches
Command: npx skills add https://github.com/D0NMEGA/donnyclaude --skill gsd-reapply-patches-d0nmega

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reapply local user modifications after a GSD update by merging your backed-up patches into the newly installed version, preserving customizations and ensuring a stable upgrade path.

Core Features & Use Cases

Three-way merge when a pristine baseline is available: compare pristine, user backup, and new version to isolate changes and preserve user edits.
Enhanced two-way fallback: when no baseline exists, apply strengthened heuristics to distinguish mechanical drift from genuine customization.
Automated patch lifecycle: locate patches, determine baseline, perform merge, and report per-file status to guide resolution.

Quick Start

Run the gsd-reapply-patches workflow to merge your backed-up patches into the updated GSD.

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 without losing my customizations?▼

The patch merge process compares a pristine baseline, your user backup, and the new version to isolate changes and preserve user edits, falling back to an enhanced two-way merge with strengthened heuristics when no baseline is available.

How does a three-way merge handle local patches during a GSD update?▼

A three-way merge during a GSD update compares a pristine baseline, your user backup, and the new version to isolate changes and preserve user edits, falling back to enhanced two-way heuristics when no baseline is available.

What happens when no pristine baseline is available for merging patches?▼

When no pristine baseline is available for merging patches, the system applies an enhanced two-way fallback using strengthened heuristics to distinguish mechanical drift from genuine customization and maintain your modifications.

Do I need git history to discover baselines for patch management?▼

You do not strictly need git history for patch management baseline discovery, as the system can locate baselines via git history or alternatively through gsd-pristine snapshots to enable proper patch merging.

How do I identify patch merge conflicts after updating my GSD baseline?▼

To identify patch merge conflicts after updating your GSD baseline, review the per-file merge reporting generated by the workflow, which provides detailed status updates to guide conflict resolution.

What's the best way to manage patch conflicts when upgrading GSD projects?▼

The best way to manage patch conflicts when upgrading GSD projects is to use an automated patch lifecycle that locates patches, determines baselines via git or snapshots, performs merges, and generates per-file status reports to guide resolution.