propose-refactors

Propose refactoring opportunities for Swift code during reviews and legacy modernization.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/saxjax/saxjaxTuner --skill propose-refactors
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: propose-refactors
Source: https://github.com/saxjax/saxjaxTuner/tree/main/.github/skills/propose-refactors
Command: npx skills add https://github.com/saxjax/saxjaxTuner --skill propose-refactors

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Swift codebases often accumulate technical debt, leading to unclear APIs, fragile architecture, and harder maintenance.

Core Features & Use Cases

  • Actionable Refactoring Guidance: Generate concrete, testable refactoring suggestions focused on clarity and performance.
  • Architectural & API Design Focus: Emphasize SRP, DRY, immutability, and clean public interfaces.
  • Code Review Context & Examples: Provide before/after examples and rationale for suggested changes.
  • Use Case: Use during code reviews, when improving legacy Swift code, or addressing common debt patterns.

Quick Start

Review the provided Swift file and generate actionable refactoring suggestions focused on clarity, maintainability, and performance.

Frequently Asked Questions about propose-refactors

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

FAQPage Schema
How do I refactor Swift code to improve maintainability and clarity?

To refactor Swift code for maintainability, analyze your file to generate actionable suggestions targeting clarity, performance, and proper architectural boundaries. This process provides concrete before/after examples and design rationale.

What is the best way to identify architectural debt in a legacy Swift codebase?

Identifying architectural debt in a legacy Swift codebase involves evaluating modules against the Single Responsibility Principle and immutability. This generates testable refactoring opportunities focused on encapsulation and proper guard usage.

Can I get refactoring suggestions for Swift code reviews that enforce design principles?

Yes, you can get refactoring suggestions for Swift code reviews that enforce design principles by applying checks for SRP, immutability, and clean public interfaces. This ensures practical API design guidelines are satisfied.

Does this approach work for improving testability and encapsulation across Swift modules?

Yes, this approach works for improving testability and encapsulation across Swift modules by proposing actionable refactoring opportunities. It addresses common debt patterns to yield a clean, maintainable architecture.

When do I need to apply Swift refactoring techniques for better API design?

You need to apply Swift refactoring techniques for better API design when your codebase accumulates technical debt, leading to unclear APIs and fragile architecture. This generates concrete, testable refactoring suggestions.

Why should I use guard statements and immutability when refactoring Swift?

You should use guard statements and immutability when refactoring Swift to satisfy requirements for the Single Responsibility Principle and practical API design. This emphasizes clean public interfaces and proper encapsulation.