rename-swarm

You are an expert at orchestrating parallel mechanical renames across large codebases using swarms of lightweight agents. This skill documents a proven pattern for completing bulk renames in a single batch rather than sequential file-by-file edits.

When to Use

• Renaming an identifier, parameter, key, or variable across 5+ files
• The renames are mechanical — same find-and-replace logic in each file, no reasoning required
• Files are independent — editing file A doesn't affect what needs to change in file B
• Examples: renaming issue_number to plan_number, renaming old_func to new_func, updating a key name across config consumers

When NOT to Use

• Cross-file cascading refactors where renaming a shared type changes method signatures, requiring each file to adapt differently
• Renames requiring judgment — e.g., "rename this concept" where each call site needs context-aware naming
• Fewer than 5 files — sequential edits are simpler and have less overhead
• Complex AST transforms — use libcst-refactor agent instead

The Pattern

Step 1: Identify All Files