fleet-cascading-fleet

Propagate wheelhouse template SHAs and registry pins across fleet repositories.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Propagate wheelhouse template changes and registry-pin chains across all fleet repositories. This skill packages the canonical fleet-repo list, the FLEET_SYNC=1 sentinel pattern, the worktree-per-repo loop, push-direct plus PR-fallback, and worktree-cleanup that survives mid-loop crashes. It is used when a wheelhouse template SHA needs to land in every fleet repo or when a registry pin chain must propagate, or when batching multiple SHAs into a single cascade wave.

Core Features & Use Cases

  • Cascade template and registry-pin changes across the fleet set with deterministic, auditable execution.
  • Two operational modes: template cascade (propagates wheelhouse/template SHA to all fleet repos) and registry-pin cascade (propagates registry pins through the fleet and registry).
  • Safe, idempotent handling with per-repo worktrees, direct-push or PR fallback, and post-cascade lockfile reconciliation.

Quick Start

Run the canonical cascade with node .claude/skills/fleet/cascading-fleet/lib/cascade-template.mts <template-sha> to propagate the change to all fleet repos.

Frequently Asked Questions about fleet-cascading-fleet

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

FAQPage Schema
How do I cascade wheelhouse template changes across multiple git repositories?

To cascade wheelhouse template changes across multiple git repositories, you propagate a specific template SHA to all fleet repos using per-repo worktrees, direct pushes, and PR fallbacks for deterministic, idempotent execution.

What is the best way to propagate registry pins through a fleet repo set?

Propagating registry pins through a fleet repo set requires a registry-pin cascade mode that threads the pin chain across all target repositories while enforcing post-cascade lockfile reconciliation and clean worktree cleanup.

Can I batch multiple template SHAs into a single cascade wave?

Yes, you can batch multiple template SHAs into a single cascade wave to coordinate propagation across the fleet set, using the FLEET_SYNC sentinel to guarantee safe, idempotent handling and post-cascade reconciliation.

How do git worktree cleanup and mid-loop crashes affect fleet cascade automation?

Fleet cascade automation survives mid-loop crashes by using per-repo git worktrees that guarantee deterministic worktree cleanup, ensuring the cascade state remains idempotent and recoverable across the fleet repositories.

Does fleet cascading support direct pushes and PR fallbacks for git workflows?

Fleet cascading supports both direct pushes and PR fallbacks for git workflows, attempting a direct push to each repository first and automatically falling back to a pull request if the push fails or is rejected.