fleet-migrating-rule-packs

Apply rule-pack transformations across target files in parallel worktrees.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates large-scale mechanical migrations by codifying repeated transformations as rule packs and applying them across many target files in parallel, dramatically reducing manual effort and risk.

Core Features & Use Cases

  • Rule-pack driven migrations: package transformations as markdown rule files and apply them consistently across a codebase.
  • Autonomous per-file workflow: each target file runs in its own worktree with isolated state, enabling safe parallel processing and rapid iteration.
  • Feedback-driven improvement: captures PR-review feedback and rewrites it into the rule pack for future migrations.

Quick Start

Process a target set of files with a rule-pack-driven migration using autonomous per-file worktrees.

Frequently Asked Questions about fleet-migrating-rule-packs

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

FAQPage Schema
How do I automate mechanical code migrations across multiple files?

Automate mechanical code migrations by codifying repeated transformations as markdown rule packs and applying them across target files in parallel. This drastically reduces manual effort and risk when updating 10 or more files.

What is a per-file worktree workflow for codebase migrations?

A per-file worktree workflow executes deterministic transformations by running each target file in its own isolated git worktree. This enables safe parallel processing, rapid iteration, and dedicated PR-based review for every changed file.

How do I scale deterministic code transformations across multiple repositories?

Scale deterministic transformations across multiple repositories by applying a rule-pack driven migration workflow. It uses parallel worktree execution to process many files simultaneously, ensuring consistent, isolated updates across your entire codebase.

Can I use pull-request review feedback to improve automated migration rules?

Yes, you can use pull-request review feedback to improve automated migration rules. The workflow captures review feedback and automatically rewrites it into the markdown rule pack for future iterations and migrations.

When should I use a rule-pack migration workflow instead of manual refactoring?

Use a rule-pack migration workflow when facing deterministic transformations that affect 10 or more files. It orchestrates large-scale, mechanical codebase changes consistently, avoiding the high manual effort and risk of individual file refactoring.

Does this migration workflow require external dependencies to process parallel worktrees?

No, this migration workflow does not require external dependencies to process parallel worktrees. It natively orchestrates isolated per-file worktree execution and PR-based review without needing additional component installations.