gsd-reapply-patches

Merge local GSD patches into updated files after an update.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/novatech2210-cmd/ImidusApp --skill gsd-reapply-patches-novatech2210-cmd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-reapply-patches
Source: https://github.com/novatech2210-cmd/ImidusApp/tree/main/.codex/skills/gsd-reapply-patches
Command: npx skills add https://github.com/novatech2210-cmd/ImidusApp --skill gsd-reapply-patches-novatech2210-cmd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

After a GSD update, local modifications may be overwritten or lost. This skill automates merging your saved changes back into the updated files, reducing manual reconciliation work.

Core Features & Use Cases

  • Detect patched files from backups and compare with the newly installed versions.
  • Perform intelligent, section-aware merges that preserve user additions while integrating upstream changes.
  • Resolve conflicts with user input and provide a clear summary of merged results.
  • Update the local manifest so future updates accurately track patches.
  • Offer cleanup options to retain or remove patch backups.

Quick Start

Run the gsd-reapply-patches command to merge your local GSD patches into the updated files.

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

To reapply local patches after an update, you need a file-by-file merge process. This Skill detects your saved changes from backups and merges them into newly installed versions, preserving local modifications while integrating upstream updates.

What happens when merging local modifications results in conflicts with the new version?

When merging local modifications results in conflicts, the process pauses to request user input for resolution. It provides a summary of conflicting changes, allowing you to decide how to integrate both your patches and upstream updates.

How do I track which files have local modifications before merging them into a new update?

To track which files have local modifications, the tool reads a local patch manifest. It detects patched files from backups, compares them with newly installed versions, and summarizes changes before performing the intelligent merge.

Can I automatically update the patch manifest after merging local changes into the new files?

Yes, you can automatically update the patch manifest after merging local changes. The tool updates the local manifest post-merge so future updates accurately track patches, and offers cleanup options to retain or remove patch backups.

What is the best way to preserve local configuration tweaks across multiple components during a version upgrade?

The best way to preserve local configuration tweaks during a version upgrade is using section-aware merges. This approach applies file-by-file merges across multiple components, ensuring user additions are preserved while integrating upstream changes.