gsd-reapply-patches

Reapply user-local patches to updated GSD installations with conflict handling.

1|Updated Aug 17, 2025
One-click install
npx skills add https://github.com/DuySeu/StockMind --skill gsd-reapply-patches-duyseu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-reapply-patches
Source: https://github.com/DuySeu/StockMind/tree/main/.agent/skills/gsd-reapply-patches
Command: npx skills add https://github.com/DuySeu/StockMind --skill gsd-reapply-patches-duyseu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reapply local modifications after a GSD update wipes and reinstalls files, merging user's saved changes back into the new version and intelligently handling cases where upstream changes occurred.

Core Features & Use Cases

  • Detect and locate local patches across common runtime directories and the project
  • Merge each edited file into the updated version with conflict resolution when the upstream version differs
  • Update the patch manifest and optionally retain or clean patch backups after reapplication

Quick Start

Run gsd-reapply-patches after a GSD update to automatically merge your local changes into 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 software update wipes my custom modifications?

To reapply local patches after an update, this automation Skill locates your saved patch backups and automatically merges those custom modifications back into the newly installed upstream files, preserving your changes without manual re-editing.

What happens when reapplying patches if the upstream version changed the same sections?

When reapplying patches and the upstream version changed the same sections, the merge process includes conflict resolution handling, allowing you to manage overlapping edits intelligently rather than blindly overwriting new upstream code.

Do I need a specific directory structure to merge local patches after an update?

You need a local patches directory structure to exist or be discoverable across common runtime directories and your project, which the tool parses for backup metadata to accurately merge changes into the current installation.

Can I automatically clean up patch backups after reapplying modifications?

Yes, after reapplying modifications and writing merged results back to your current installation, the tool updates the patch manifest and optionally retains or cleans the patch backups based on your preference.

What is the best way to preserve version control modifications across multiple installation contexts?

The best way to preserve version control modifications across multiple installation contexts is to automate the backup discovery and merging process, which scans common runtime directories to reapply your local patches to the updated files.