Results for “safe-refactoring”

Guides incremental code improvements, error-proofing through types and validation, and standardization for higher code quality.

Enforce idiomatic Rust patterns for ownership, error handling, enums, traits, concurrency, and best practices to build safe, performant applications.

Guides incremental code improvements, error-proofing through types and validation, and standardization for higher quality and fewer defects.

Reviews a codebase for structural smells and refactors them with provable safety, using micro commits and green-bar discipline.

Safe refactor planning for Nick's codebases. Use when planning large refactors, reducing blast radius, sequencing cleanup work, or deciding how to improve messy code without breaking product velocity.

Surgical code refactoring to improve maintainability without changing behavior. Covers extracting functions, renaming variables, breaking down god functions, improving type safety, eliminating code smells, and applying design patterns. Less drastic than repo-rebuilder; use for gradual improvements.

Improve code structure and readability without changing external behavior through surgical refactoring techniques.

Surgical code refactoring to improve maintainability without changing behavior. Covers extracting functions, renaming variables, breaking down god functions, improving type safety, eliminating code smells, and applying design patterns. Less drastic than repo-rebuilder; use for gradual improvements.

Use when the user wants to rename, extract, split, move, or restructure code safely. Examples: "Rename this function", "Extract this into a module", "Refactor this class", "Move this to a separate file"

Executes automated refactoring for specific files, directories, or semantic queries. This skill should be used when the user asks to refactor specific files or directories, simplify recently changed code, clean up dead code in a limited scope, or invokes "/refactor".

Executes automated project-wide refactoring with a focus on cross-file optimization. This skill should be used when the user asks for project-wide refactoring, cross-file simplification, consistency standardization across the codebase, duplication reduction, or invokes "/refactor-project".

Improves structure without behavior changes, using tests and focused slices; not for features unless behavior change is explicit.

Modernizes legacy scripts (bash, Node, Python) by replacing deprecated APIs, adding error handling, converting callbacks to async/await, and improving maintainability. Turns brittle one-off scripts into reliable, documented tools.

Refactoring Analyst

Plan a multi-file refactor with proper sequencing and rollback steps

Review and refactor code according to project-specific coding guidelines and instructions.

Reduces cognitive complexity of a specified method by extracting logic into focused helper methods, improving readability and maintainability.

Creates a concrete, multi-phase plan before starting a multi-file refactor, including affected files, dependencies, verification steps, and rollback procedures.

Refactors code for better readability, performance, and maintainability

Refactors code by renaming variables, methods, classes, and types to improve clarity and intent, with automatic testing and commits after each rename.

Refactors Swift code toward declarative functional programming with immutability, value types, pure functions, transformations, and closure-based APIs.

Refactors test files to improve behavioral coverage, clarity, structure, assertions, fixture setup, and mocking strategy, removing implementation-detail or low-value tests.

Create a detailed refactor plan with tiny commits via user interview, then file it as a GitHub issue. Use when user wants to plan a refactor, create a refactoring RFC, or break a refactor into safe incremental steps.

Plan and execute large refactor or rewrite efforts efficiently with parallel multi-agent analysis and implementation.

Use when restructuring code for maintainability while preserving external behavior.

Analyze a codebase with specialized agents and propose refactoring tickets.

Generates Spring Boot 3.x configurations, REST controllers, Spring Security 6 authentication flows, Spring Data JPA repositories, and reactive WebFlux endpoints for building microservices and reactive Java applications.

Use when code is hard to read, has duplication, is too complex, has grown beyond 300 lines, or needs restructuring without changing behavior. For extracting functions, simplifying nested logic, removing dead code, improving naming, splitting large files, and applying clean code principles. Activate when user says "clean this up", "this is messy", "simplify", "extract", or "improve readability".

Harness TDD

Use when the user wants to rename, extract, split, move, or restructure code safely. Examples: "Rename this function", "Extract this into a module", "Refactor this class", "Move this to a separate file"