name	batch-refactor-with-sub-agents
description	Use a sub-agent (like `generalist`) to perform repetitive code transformations across multiple files in a single turn.

When to Use

Renaming symbols or updating function signatures across many files.
Migrating code from one pattern to another (e.g., manual error handling to a common helper).
Replacing literals with centralized constants across the codebase.
Performing any repetitive "find-and-replace" task that would otherwise require many sequential replace calls.

Procedure

Define the transformation: Identify the exact "before" and "after" patterns. Create a representative code snippet for the sub-agent to follow.
Locate targets: Use grep_search to find all absolute file paths and line numbers that need modification.
Draft a precise prompt: Call the generalist (or similar) tool with a prompt that includes:
- Goal: Clear statement of the refactoring objective.
- Scope: A bulleted list of absolute file paths to modify.
- Example: A code block showing the old_string vs new_string transformation.
- Constraints: Instructions to preserve specific logic (e.g., "preserve original closure logic while changing the call site").
- Verification: Instructions to run cargo check --all-targets or specific tests after finishing.
Delegate: Execute the sub-agent call.
Review and Cleanup: Sub-agents may introduce minor issues like unused_import warnings. Perform a final sweep with cargo clippy and fix manually or via a second batch call.

Pitfalls and Fixes

symptom: Sub-agent misses some files or applies incorrect logic.
likely cause: Prompt was too vague or the transformation was too complex for a single turn.
fix: Break the task into smaller, more homogeneous batches (e.g., "refactor all files in directory A first").
symptom: cargo check fails after the sub-agent finishes.
likely cause: Sub-agent clobbered a symbol or messed up indentation/syntax.
fix: Read the modified files and use targeted replace calls to fix the syntax errors.

Verification

Run cargo check --all-targets to confirm zero compilation errors.
Run cargo clippy --all-targets to find and fix any unused_import or style warnings introduced by the refactor.
Run relevant integration tests for the modified files.

Más de este repositorio

mismo repositorio

check-code-quality

r3bl-org/r3bl-open-core

Run comprehensive Rust code quality checks including compilation, linting, documentation, and tests. Use after completing code changes and before creating commits.

2026-07-05475

remove-crate-prefix

r3bl-org/r3bl-open-core

Enforce the "Clean Imports over Inline Absolute Paths" rule by removing inline crate:: prefixes and adding proper use statements.

2026-07-05475

create-commit-message

r3bl-org/r3bl-open-core

Rules and guidelines for creating well-formatted commit messages, including 72-char limits, scope prefixes, and trailer blocks for tasks, PR closing, and attribution.

2026-06-30475

fast-string-allocations

r3bl-org/r3bl-open-core

Zero-allocation string building strategies. Use when formatting strings, generating ANSI codes, or writing hot loops to avoid heap allocations and Formatter state machine overhead.

2026-06-30475

run-clippy

r3bl-org/r3bl-open-core

Run clippy linting, enforce comment punctuation rules, format code with cargo fmt, and verify module organization patterns. Use after code changes and before creating commits.

2026-06-30475

write-structured-tracing

r3bl-org/r3bl-open-core

Standard for writing structured tracing logs behind debug flags.

2026-06-30475

name	batch-refactor-with-sub-agents
description	Use a sub-agent (like `generalist`) to perform repetitive code transformations across multiple files in a single turn.

When to Use

Renaming symbols or updating function signatures across many files.
Migrating code from one pattern to another (e.g., manual error handling to a common helper).
Replacing literals with centralized constants across the codebase.
Performing any repetitive "find-and-replace" task that would otherwise require many sequential replace calls.

Procedure

Define the transformation: Identify the exact "before" and "after" patterns. Create a representative code snippet for the sub-agent to follow.
Locate targets: Use grep_search to find all absolute file paths and line numbers that need modification.
Draft a precise prompt: Call the generalist (or similar) tool with a prompt that includes:
- Goal: Clear statement of the refactoring objective.
- Scope: A bulleted list of absolute file paths to modify.
- Example: A code block showing the old_string vs new_string transformation.
- Constraints: Instructions to preserve specific logic (e.g., "preserve original closure logic while changing the call site").
- Verification: Instructions to run cargo check --all-targets or specific tests after finishing.
Delegate: Execute the sub-agent call.
Review and Cleanup: Sub-agents may introduce minor issues like unused_import warnings. Perform a final sweep with cargo clippy and fix manually or via a second batch call.

Pitfalls and Fixes

symptom: Sub-agent misses some files or applies incorrect logic.
likely cause: Prompt was too vague or the transformation was too complex for a single turn.
fix: Break the task into smaller, more homogeneous batches (e.g., "refactor all files in directory A first").
symptom: cargo check fails after the sub-agent finishes.
likely cause: Sub-agent clobbered a symbol or messed up indentation/syntax.
fix: Read the modified files and use targeted replace calls to fix the syntax errors.

Verification

Run cargo check --all-targets to confirm zero compilation errors.
Run cargo clippy --all-targets to find and fix any unused_import or style warnings introduced by the refactor.
Run relevant integration tests for the modified files.