cascading-fleet

Name: cascading-fleet
Availability: InStock
Author: Socket

Propagate wheelhouse template changes to fleet repositories with worktrees and PR fallback.

125|42|Updated May 19, 2025

Search Tags:#automation #deployment #git-worktree #cascade #pinning #fleet #wheelhouse

Ready to run

npx skills add https://github.com/SocketDev/socket-mcp --skill cascading-fleet

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: cascading-fleet
Source: https://github.com/SocketDev/socket-mcp/tree/main/.claude/skills/fleet/cascading-fleet
Command: npx skills add https://github.com/SocketDev/socket-mcp --skill cascading-fleet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cascading wheelhouse template changes to every fleet repository to ensure consistent template landings and registry-pin propagation across the fleet.

Core Features & Use Cases

Automates per-repo cascade execution with worktrees, pushing directly or creating PRs when direct push is blocked.
Supports both template cascades and registry-pin cascades to propagate changes through the fleet.
Includes safety guards and recovery steps to handle mid-loop crashes and lockfile reconciliation after cascade.

Quick Start

Run the canonical cascade to propagate a template SHA to all fleet repos and monitor per-repo results.

Frequently Asked Questions about cascading-fleet

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

FAQPage Schema

How do I propagate a wheelhouse template SHA to all fleet repositories?▼

You can propagate a wheelhouse template SHA to all fleet repositories by running a canonical cascade that updates every repo with worktree management, applying direct pushes or PR fallbacks to ensure consistent template landings across the fleet.

What is registry-pin chain propagation and when do I need it?▼

Registry-pin chain propagation ensures consistent dependency versions across your fleet. You need it when a registry pin chain requires updates across multiple repositories to maintain deployment consistency and configuration alignment.

How do I handle lockfile reconciliation after a cascade across fleet repos?▼

Lockfile reconciliation after a cascade is handled automatically through postcascade steps that validate and fix lockfiles, ensuring dependency consistency across all fleet repositories once the template or pin propagation completes.

Can I use git worktrees for per-repo cascade execution?▼

Yes, per-repo cascade execution supports git worktrees, allowing isolated repository updates during template or registry-pin cascades while maintaining safety guards and sentinel checks for each repository in the fleet.

What happens if a direct push is blocked during a fleet cascade?▼

When a direct push is blocked during a fleet cascade, the system automatically falls back to creating pull requests, ensuring the template or registry-pin changes still propagate to the target repository safely.

How does FLEET_SYNC gating work with sentinel guards?▼

FLEET_SYNC gating uses sentinel guards to control and protect cascade execution per repository, preventing mid-loop crashes and ensuring safe propagation of template or registry-pin changes across the entire fleet.