gpd-reapply-patches

Merge saved local GPD patches into updated installations with conflict handling.

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/MichaelsEngineering/get-physics-done-test --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/get-physics-done-test/tree/main/.agents/skills/gpd-reapply-patches
Command: npx skills add https://github.com/MichaelsEngineering/get-physics-done-test --skill gpd-reapply-patches-michaelsengineering

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

After a GPD update wipes and reinstalls files, researchers risk losing local modifications. This Skill automates reapplying saved patches and merging user edits back into the updated version, preserving research-specific customizations.

Core Features & Use Cases

  • Detects local patches and reads backup metadata to plan merges.
  • Merges user changes into the new upstream versions with conflict resolution prompts.
  • Updates the manifest and offers cleanup options to maintain reproducible workflows.
  • Use Case: A tokamak control experiment updates GPD; this tool re-applies the developer's custom patches.

Quick Start

Run gpd-reapply-patches to merge your saved local patches back into the updated GPD installation.

Frequently Asked Questions about gpd-reapply-patches

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

FAQPage Schema
How do I reapply local patches after a GPD update overwrites them?

To reapply local patches after a GPD update, use an automated merge tool that reads backup metadata to detect modifications and merges user changes back into the new upstream version with conflict resolution prompts.

What is the best way to preserve local GPD modifications across software updates?

The best way to preserve local GPD modifications is using a patch reapplication workflow that automatically detects custom patches, merges user edits into updated installations, and updates the manifest to maintain reproducible results.

How does conflict resolution work when merging custom GPD patches into an updated installation?

Conflict resolution during GPD patch merging works by detecting local patches, reading backup metadata to plan merges, and providing interactive conflict resolution prompts to ensure user changes are preserved.

Can I automate merging custom templates and workflow tweaks into a new GPD version?

Yes, you can automate merging custom templates and workflow tweaks into a new GPD version by running a patch reapplication tool that handles patch detection, conflict handling, and manifest maintenance deterministically.

Does reapplying GPD patches update the manifest to maintain reproducible research workflows?

Yes, reapplying GPD patches updates the manifest automatically and offers cleanup options to ensure that research-specific customizations and deterministic results are maintained across updates.