gpd-reapply-patches

Reapply backed-up local modifications to GPD files after an update reinstall.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/MichaelsEngineering/sentinel-multiscale-field-dynamics --skill gpd-reapply-patches-michaelsengineering
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gpd-reapply-patches
Source: https://github.com/MichaelsEngineering/sentinel-multiscale-field-dynamics/tree/main/.agents/skills/gpd-reapply-patches
Command: npx skills add https://github.com/MichaelsEngineering/sentinel-multiscale-field-dynamics --skill gpd-reapply-patches-michaelsengineering

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After a GPD update wipes and reinstalls workflow, command, and agent files, any local customizations you made are lost. This Skill merges your previously backed-up modifications back into the newly installed versions, handling cases where the upstream file also changed. ## Core Features & Use Cases - Patch Detection and Summary: Locates the gpd-local-patches backup directory, reads backup-meta.json, and presents a table of files pending reapplication with version context. - Intelligent Three-Way Merge: Compares your backed-up copy against the newly installed file, applies your additions and modifications, skips files already incorporated upstream, and flags conflicts for user resolution. - Physics Content Preservation: Pays special attention to sign conventions, unit definitions, and notation choices so silent changes do not introduce calculation errors. - Use Case: You customized validation checks and notation conventions in GPD workflow files, then ran a GPD update. Invoke this Skill to merge those customizations back into the fresh installation, resolve any conflicts interactively, and optionally clean up the patch backups. ## Quick Start Ask the assistant to reapply my saved local GPD patches after the update and show me the merge status for each file.

Frequently Asked Questions about gpd-reapply-patches

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I restore my local GPD customizations after an update?▼

Run the reapply-patches workflow, which reads backup-meta.json from the gpd-local-patches directory and merges your saved modifications into the newly installed files. Each file is reported as Merged, Skipped, or Conflict resolved.

What happens when both my patch and the upstream file changed?▼

The merge flags the file as a conflict, shows both versions side by side, and asks you which version to keep. Your chosen resolution is then written to the installed location and reported in the final status table.

Where are GPD local patch backups stored?▼

Backups are stored in ./.codex/gpd-local-patches for project scope, falling back to the global ~/.codex/gpd-local-patches directory. They are created automatically when you run gpd-update after modifying GPD workflow, command, or agent files.

Why does reapply-patches say no local patches found?▼

This message appears when no gpd-local-patches directory or backup-meta.json exists in either the project or global location. It means no modifications were backed up during the last update, so there is nothing to reapply.

Can I delete the patch backups after reapplying them?▼

Yes. After all patches are processed, the workflow asks whether to keep the gpd-local-patches directory for reference or remove it. Keeping backups is safer if you expect further manual adjustments.