Verified:GitHub

gsd-reapply-patches

Reapplies saved local patches after a GSD update overwrites customized files.

264|11|Updated Apr 25, 2026

Search Tags:#conflict resolution #three-way merge #patch recovery #update migration #workflow restoration #local modifications

Ready to run

npx skills add https://github.com/coco-research/coco --skill gsd-reapply-patches-coco-research

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gsd-reapply-patches
Source: https://github.com/coco-research/coco/tree/main/systems/gsd/skills/gsd-reapply-patches
Command: npx skills add https://github.com/coco-research/coco --skill gsd-reapply-patches-coco-research

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill restores your previously saved local modifications after a GSD update overwrites files, so you do not lose custom workflow changes or have to rebuild them manually.

Core Features & Use Cases

Three-way merge recovery: Compares the pristine baseline, the backed-up user version, and the newly installed version to preserve intentional edits.
Conflict detection: Surfaces overlapping upstream and user changes for review instead of silently discarding anything.
Verification safeguards: Checks for dropped hunks after merging and warns when content may be missing.
Use case: Reapply customized workflow, command, or agent files after reinstalling a GSD update while keeping track of what changed.

Quick Start

Use the gsd-reapply-patches skill to reapply your saved local modifications after a GSD update and review any conflicts.

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 workflow update overwrites my files?▼

Patch recovery uses a three-way merge to compare the pristine baseline, your backed-up user version, and the newly installed files. It preserves intentional edits while surfacing overlapping upstream changes for manual conflict resolution.

What is a three-way merge for patch recovery and how does it handle conflicts?▼

A three-way merge compares the original baseline, your saved local version, and the new update to identify intentional changes. Instead of silently discarding edits, it detects overlapping upstream and user modifications and surfaces them as conflicts for review.

How do I reapply saved patches to customized command and agent files after reinstalling?▼

You reapply saved patches by running this skill across your config directories. It merges your custom command and agent file edits into the refreshed versions and verifies that no content hunks were dropped during the workflow restoration process.

Does update migration silently overwrite my custom workflow changes without warning?▼

No, update migration does not silently overwrite changes. This skill detects overlapping upstream and user modifications, surfacing them explicitly as conflicts for review to ensure intentional local modifications are safely preserved during the update.

What happens if hunks are dropped during the three-way merge of local patches?▼

If hunks are dropped during the merge, verification safeguards catch the missing content. The skill performs post-merge verification and warns you when content may be missing, ensuring no intentional changes are lost silently.

When do I need to use conflict resolution for local modifications in config directories?▼

You need conflict resolution for local modifications when a GSD update overwrites customized workflow, command, or agent files across config directories. It is required to safely merge user edits into refreshed files without losing intentional changes.