skills.rest
ArtRiv
ArtRivCOMMUNITY
Explore all skills by this author →
GitHub

gsd-reapply-patches

Merge saved GSD local patches into newly installed workflow files.

Updated Feb 11, 2026
Search Tags:#conflict resolution#patch management#version updates#gsd#workflow customization#merge automation
One-click install
npx skills add https://github.com/ArtRiv/game-topicos-especiais --skill gsd-reapply-patches-artriv
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-reapply-patches
Source: https://github.com/ArtRiv/game-topicos-especiais/tree/main/.github/skills/gsd-reapply-patches
Command: npx skills add https://github.com/ArtRiv/game-topicos-especiais --skill gsd-reapply-patches-artriv

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

A GSD update can wipe and reinstall workflow, command, or agent files, causing your local edits to disappear even though you intentionally customized them.

Core Features & Use Cases

  • Reapplies backed-up local modifications: Reads previously saved patches and merges them back into the newly installed upstream files.
  • Intelligent merge with conflict detection: Skips changes already incorporated upstream, and flags conflicts when both upstream and your local version changed the same section.
  • Version-aware patch reporting: Shows which files were pending, merged, skipped, or in conflict so you can verify the outcome.

Quick Start

Ask the assistant to run the gsd-reapply-patches skill to merge your saved GSD local patches back into the current installed 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 restore local workflow customizations after a GSD update overwrites them?▼

To restore local workflow customizations after a GSD update, you can reapply saved patches by reading backup metadata and merging backed-up file contents into newly installed upstream files.

How does patch management handle merge conflicts during version updates?▼

Patch management handles merge conflicts during version updates by performing section-level comparisons between local backups and upstream files, then flagging conflicts when both versions modify the same section.

How do I reapply local patches to updated workflow files?▼

To reapply local patches to updated workflow files, trigger the skill to read a detected local patches directory, compare backed-up contents against new versions, and automatically merge safe modifications.

Why does my GSD update wipe out local edits to command and agent files?▼

A GSD update wipes out local edits because it reinstalls upstream workflow, command, and agent files over existing ones, requiring previously saved patch backups to restore your intentional customizations.

Can I track which local patches were skipped or merged after updating?▼

Yes, you can track which local patches were skipped or merged through version-aware patch reporting, which displays file statuses including pending, merged, skipped, or in conflict.

Do I need a backup-meta.json file to restore local modifications?▼

Yes, you need a backup-meta.json file located within a detected local patches directory to compare backed-up and newly installed file contents for safe section-level merging.

Related Skills

Explore More Software Engineering Skills→
ev3rlitev3rlit

gsd-reapply-patches

Merge local patch backups into a fresh GSD installation after an upgrade.

Community
Advanced
dlantsdlants
462

update-permissions

Merge commandConfig entries into Magenta options.json files.

Community
Basic
Pear-CommercePear-Commerce

gsd-update

Update npm-installed GSD workflow tools after reviewing the changelog.

Official
Intermediate
gujiachun-rainbowgujiachun-rainbow
8

Pulling Updates from Skills Repository

Sync local skills repository with upstream changes while preserving local modifications.

Community
Intermediate