regenerating-patches

Regenerate fleet 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 regenerating-patches
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: regenerating-patches
Source: https://github.com/SocketDev/socket-mcp/tree/main/.claude/skills/fleet/regenerating-patches
Command: npx skills add https://github.com/SocketDev/socket-mcp --skill regenerating-patches

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill regenerates plugin-cache patches in scripts/fleet/plugin-patches/ against the pinned upstream plugin source when patches 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

  • Regenerate and align fleet plugin patches with the currently pinned upstream source.
  • Validate patches with patch -p1 --dry-run against the pristine files to ensure correctness.
  • Apply patches to re-establish a clean, consistent plugin-cache state after SHA changes.

Quick Start

Run regenerating-patches to refresh all stale fleet patches against the pinned upstream sources.

Frequently Asked Questions about regenerating-patches

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

FAQPage Schema
How do I fix a plugin patch that no longer applies after a SHA bump?

Validate plugin patches by running patch -p1 --dry-run against the pristine upstream files to ensure correctness before applying them to the plugin-cache.

What is the best way to keep plugin-cache patches in sync with upstream source?

You need access to the pinned SHAs from .claude-plugin/marketplace.json, the patch diffs in scripts/fleet/plugin-patches, and the patching tool patch -p1 to validate and regenerate patches.

When do I need to regenerate fleet plugin patches?

The regenerating-patches process applies when a plugin's source.sha bumps in marketplace.json or when install-claude-plugins.mts warns that a patch no longer applies, covering all fleet patches.

Does regenerating patches require access to the marketplace.json file?

Yes, regenerating patches requires access to the pinned SHAs from .claude-plugin/marketplace.json, patch diffs in scripts/fleet/plugin-patches, and the patch -p1 tool to validate and regenerate patches.