fleet-regenerating-patches

Regenerate stale plugin-cache patches against pinned upstream plugin sources.

125|42|Updated May 19, 2025
One-click install
npx skills add https://github.com/SocketDev/socket-mcp --skill fleet-regenerating-patches
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fleet-regenerating-patches
Source: https://github.com/SocketDev/socket-mcp/tree/main/.agents/skills/fleet-regenerating-patches
Command: npx skills add https://github.com/SocketDev/socket-mcp --skill fleet-regenerating-patches

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Regenerates the wheelhouse-owned plugin-cache patches in scripts/fleet/plugin-patches/ against the pinned upstream plugin source when they go stale after a plugin SHA bump. Use when install-claude-plugins.mts warns that a patch no longer applies, or after bumping a plugin's source.sha in marketplace.json.

Core Features & Use Cases

  • Phase-driven patch regeneration to maintain compatibility with pinned upstream sources.
  • Detects stale patches and regenerates them to reapply cleanly against the current plugin.
  • Use Case: When a plugin's source.sha changes, run this workflow to refresh all related patches and keep the fleet plugin cache in sync.

Quick Start

Run the fleet-regenerating-patches workflow after updating a plugin SHA to refresh patches.

Frequently Asked Questions about fleet-regenerating-patches

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

FAQPage Schema
How do I regenerate stale plugin-cache patches after a plugin SHA bump?

Regenerate stale plugin-cache patches by running the fleet-regenerating-patches workflow against the pinned upstream plugin source. It refreshes patches in scripts/fleet/plugin-patches to reapply cleanly after a source.sha change in marketplace.json.

What causes a patch to no longer apply during plugin installation?

A patch no longer applies when the plugin's source.sha changes in marketplace.json, making existing patches stale against the new pinned upstream tree. The install-claude-plugins.mts script reports this mismatch, signaling that patch regeneration is needed.

How does patch validation work before updating upstream plugin sources?

Patch validation performs a forward dry-run against the pristine pinned-SHA tree to confirm changes apply cleanly. After validation, it updates patch headers to reflect the new SHA and plugin version, ensuring fleet plugin cache integrity.

When should I run a patch regeneration workflow for fleet plugins?

Run patch regeneration when install-claude-plugins.mts warns a patch no longer applies, or immediately after bumping a plugin's source.sha in marketplace.json. This keeps the fleet plugin cache synchronized with the updated upstream source.

Can I automate patch regeneration across multiple fleet plugins at once?

Yes, the phase-driven patch regeneration workflow detects stale patches across the fleet and regenerates them to reapply cleanly against the current pinned upstream sources, maintaining compatibility for all affected plugin-cache patches simultaneously.

Why do my plugin patches fail to apply after updating marketplace.json?

Patches fail because updating source.sha in marketplace.json pins a new upstream plugin version, making existing patches stale. Regenerating patches against the pristine pinned-SHA tree resolves the mismatch and updates patch headers accordingly.