rename-loop

Renames loop configuration files and updates all related references across YAML, tests, and docs.

7|2|Updated Jan 3, 2026
One-click install
npx skills add https://github.com/BrennonTWilliams/little-loops --skill rename-loop
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rename-loop
Source: https://github.com/BrennonTWilliams/little-loops/tree/main/skills/rename-loop
Command: npx skills add https://github.com/BrennonTWilliams/little-loops --skill rename-loop

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Renaming a loop in a complex project often leads to broken references in YAML configurations, test suites, and documentation. This skill automates the entire refactoring process, ensuring consistency and preventing manual errors.

Core Features & Use Cases

  • Atomic Renaming: Handles file system moves for both project-level and built-in loop definitions.
  • Global Reference Updates: Automatically scans and updates references in YAML files, test scripts, and markdown documentation.
  • Safety Guardrails: Includes dry-run capabilities, active process detection to prevent renaming running loops, and user confirmation prompts.

Quick Start

Use the rename-loop skill to change the loop name from old-task to new-task and update all associated project files.

Frequently Asked Questions about rename-loop

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

FAQPage Schema
How do I safely rename a loop and update all YAML configuration references?

To safely rename a loop, you can automate the refactoring process to update all corresponding references across YAML definitions, test suites, and documentation using atomic file system operations and text replacements.

What is the best way to handle refactoring loop configuration files without breaking test suites?

Refactoring loop configuration files without breaking test suites is handled by global reference updates, which automatically scans and updates references in YAML files, test scripts, and markdown documentation.

Can I rename a built-in loop scope or does this only work for project-specific loops?

You can rename both project-specific and built-in loop scopes, as the renaming operation handles file system moves for both levels of loop definitions while enforcing safety checks.

Do I need git to perform atomic file system moves when renaming a loop?

Yes, you need git and standard bash utilities to perform atomic file system operations and text replacements required for the renaming process.

What happens if I try to rename a loop that has active processes running?

Renaming a loop with active processes running is blocked by safety guardrails that include active process detection to prevent renaming running loops and user confirmation prompts.

Does the loop renaming process support a dry-run mode to check for naming conflicts before applying changes?

Yes, the loop renaming process supports a dry-run mode to check for naming conflicts and review changes before performing atomic file system operations and text replacements.