refactor-code
Refactor code with safety checks and pattern application. Use when user says "refactor this code", "clean up this function", "simplify this logic", "extract this into a separate function", "apply the strategy pattern here", "reduce the complexity of this module", or "reorganize this file structure".
What this skill does
# Code Refactorer Orchestrate sophisticated refactoring through multi-agent coordination with safety checks. ## Refactoring Strategies | Strategy | Risk | Use When | | ------------------ | ------ | -------------------------------------- | | **Safe** (default) | Low | Production code, critical paths | | **Aggressive** | Medium | Comprehensive restructuring with tests | | **Architectural** | High | System-wide pattern application | ## Execution Steps 1. **Understand scope** — Read the target file(s). Run `git diff HEAD` to see any uncommitted state. Use `code-explainer-agent` if the codebase context is complex. 2. **Create a task plan** — Use TodoWrite to list the refactoring tasks before starting. 3. **Dispatch refactorer-agent** — Pass: - `paths`: file(s) or globs to refactor - `goals`: e.g., `["readability", "maintainability"]` (or user-specified goal from Goals table below) - `refactor_depth`: `"surface"` | `"moderate"` | `"deep"` based on strategy - `risk_tolerance`: `"low"` | `"medium"` | `"high"` matching the strategy 4. **Apply patches** — Write the refactored code to disk using the patches returned by refactorer-agent. Apply incrementally — one logical change at a time. 5. **Enforce style** — Dispatch `style-enforcer-agent` on the modified files. 6. **Validate** — Run `git diff HEAD` to review the final changes. Confirm behavior is preserved. 7. **Generate tests** (if not already covered) — Dispatch `test-writer-agent` to add regression tests for refactored code. ## Goals - `readability`: Extract expressions, rename for clarity - `performance`: Algorithm improvements, caching - `maintainability`: SOLID principles, reduce coupling - `testability`: Dependency injection, pure functions - `all`: Comprehensive improvement ## Output Format Provides: - Summary with metrics and risk assessment - Analysis of current issues and patterns - Incremental patches with diffs - Migration plan for architectural changes - Validation results ## Safety - Small, reviewable patches - Dependency ordering - Rollback procedures - Validation checkpoints
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.