gsd-reapply-patches

Reapply backed-up local modifications to GSD files after an update reinstalls them.

Updated Feb 18, 2026
One-click install
npx skills add https://github.com/jjchambers80/judgesdirectory --skill gsd-reapply-patches-jjchambers80
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-reapply-patches
Source: https://github.com/jjchambers80/judgesdirectory/tree/main/.github/skills/gsd-reapply-patches
Command: npx skills add https://github.com/jjchambers80/judgesdirectory --skill gsd-reapply-patches-jjchambers80

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After a GSD update wipes and reinstalls workflow, command, and agent files, any local customizations you made are lost. This Skill restores those modifications by merging your backed-up copies into the newly installed versions. ## Core Features & Use Cases - Patch Detection: Locates the gsd-local-patches backup directory across multiple runtime config locations (opencode, gemini, claude) and reads backup-meta.json. - Intelligent Merge: Compares each backed-up file against the newly installed version, applies your additions, skips changes already incorporated upstream, and flags conflicts for manual resolution. - Status Reporting & Cleanup: Produces a per-file report (Merged, Skipped, Conflict) and optionally removes the patch backup directory. - Use Case: You customized a GSD agent prompt, then ran a GSD update that overwrote it. Run this Skill to merge your custom prompt sections back into the new upstream version without losing upstream improvements. ## Quick Start Reapply my saved local patches from the last GSD update and show me which files were merged or had 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 my customizations after a GSD update?▼

Run the reapply-patches command after updating. It reads the gsd-local-patches backup directory, compares each saved file with the newly installed version, and merges your modifications back in, reporting Merged, Skipped, or Conflict status per file.

Where are GSD local patch backups stored?▼

Backups are stored in a gsd-local-patches directory under your runtime config location, such as ~/.config/opencode, ~/.opencode, ~/.gemini, or a local .github, .claude directory. The Skill checks each of these paths automatically.

What happens when a GSD patch conflicts with upstream changes?▼

When a section you modified was also changed upstream, the merge flags it as a conflict. Both versions are shown and you choose which one to keep, so no change is silently overwritten.

Why does reapplying patches say nothing to reapply?▼

This message appears when no gsd-local-patches directory or backup-meta.json is found. Patches are only created when you run the GSD update command after modifying workflow, command, or agent files.

Can I delete the patch backups after reapplying them?▼

Yes. After reapplying, the Skill asks whether to keep the gsd-local-patches directory for reference or remove it. Keeping it is safe if you want a fallback copy of your modifications.