skills.rest
Pear-Commerce
Pear-CommerceOFFICIAL
Explore all skills by this author →
WebsiteGitHub

gsd-reapply-patches

Merge user-created local modifications into updated GSD workflow files.

Updated May 15, 2026
Search Tags:#merge conflicts#gsd#workflow customization#patch reapply#local modifications#update recovery
One-click install
npx skills add https://github.com/Pear-Commerce/pear-ai-skills --skill gsd-reapply-patches-pear-commerce
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-reapply-patches
Source: https://github.com/Pear-Commerce/pear-ai-skills/tree/main/skills/gsd-reapply-patches
Command: npx skills add https://github.com/Pear-Commerce/pear-ai-skills --skill gsd-reapply-patches-pear-commerce

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When you run a GSD update, any custom modifications you made to GSD workflow, command, or agent files are erased, forcing you to manually redo all your tweaks from scratch.

Core Features & Use Cases

  • Intelligent Patch Merging: Automatically detects your backed-up local modifications and merges them with the new post-update file versions, even if the upstream files have changed.
  • Conflict Resolution: Flags conflicts when a section you modified was also changed upstream, and asks you to choose which version to keep.
  • Use Case: You added custom validation logic to a GSD phase file, then ran a GSD update. This skill will merge your validation tweak into the new version of the phase file without overwriting upstream changes or losing your work.

Quick Start

Use the gsd-reapply-patches skill immediately after running a GSD update to restore all your custom workflow modifications.

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 to GSD workflow files after an update overwrites them?▼

To restore local modifications after an update, reapply your backed-up patches to the newly installed GSD file versions. This merges your custom phase files, command definitions, and agent configurations into the updated workflow without losing your tweaks.

What happens when a GSD update changes a workflow phase file that I also customized?▼

When an upstream update changes a file you customized, the patch reapply process flags the conflict. It asks you to choose which version to keep, ensuring your custom validation logic is preserved or updated without blindly overwriting either side.

Can I automatically merge custom command definitions with new GSD versions?▼

Yes, you can automatically merge custom command definitions with new GSD versions. The intelligent patch merging detects your backed-up local modifications and integrates them into the updated files, even if the upstream workflow files have changed.

Do I need a patch backup directory before restoring custom GSD changes?▼

Yes, you need a local patch backup directory containing your custom modifications. The merge operation requires access to both this backup directory and the newly installed GSD file versions to intelligently restore your workflow configurations.

When should I run a patch reapply for my GSD workflow customization?▼

You should run a patch reapply immediately after running a GSD update. This ensures all your custom workflow modifications, phase file tweaks, and agent configurations are restored before you resume working with the updated system.

Related Skills

Explore More Software Engineering Skills→
ArtRivArtRiv

gsd-reapply-patches

Merge saved GSD local patches into newly installed workflow files.

Community
Advanced
marcmontecalvomarcmontecalvo

bmad-customize

Create and verify TOML configuration overrides for BMad agents and workflows.

Community
Advanced
novatech2210-cmdnovatech2210-cmd

gsd-reapply-patches

Merge local GSD patches into updated files after an update.

Community
Advanced
NUbivekNUbivek

gsd-reapply-patches

Reapply local modifications to GSD files after an update.

Community
Intermediate