refactor
Use when refactoring, cleaning up code, reducing complexity, fixing code smells, or improving code quality. Audits TS/JS for dead code, nesting, and patterns.
What this skill does
You are an expert code reviewer focused on refactoring. Read individual rule files in `rules/` for detailed explanations and code examples. ## Rules Overview | Section | Prefix | Rules | |---|---|---| | General Patterns | `general-` | dead-code, deep-nesting, long-functions, magic-values, boolean-params, duplication | | TypeScript/JS Idioms | `ts-` | type-assertions, optional-chaining, nullish-coalescing, barrel-reexports, enum-union, async-await | | Design Principles | `design-` | single-responsibility, interface-segregation, god-objects, tight-coupling | ## Workflow ### Step 1: Audit Scan the target scope (specific files, directory, or full codebase) for violations: **General Patterns**: - Commented-out code blocks - Functions exceeding ~40 lines - Nesting deeper than 3 levels - Hardcoded numbers/strings used in conditions or timeouts - Boolean parameters in function signatures **TypeScript/JS Idioms**: - `as` type assertions (excluding test files) - Chained `&&` for null checks where `?.` applies - `||` used for defaults where `??` is safer - Barrel `index.ts` re-export files (hurt tree-shaking, slow bundlers, risk circular deps) - String enums that could be union types - `.then()` chains in async code **Design Principles**: - Files with >10 named exports - Interfaces with >7 methods - Files importing from >5 sibling modules in the same layer ### Step 2: Report List all findings grouped by category: ``` ## Refactoring Audit Results ### General Patterns - `src/services/order.ts:45` - Function `processOrder` is 62 lines → extract validation and submission - `src/utils/helpers.ts:12-18` - Commented-out code block → remove ### TypeScript/JS Idioms - `src/api/client.ts:23` - `as UserResponse` → add type guard - `src/config.ts:8` - `port || 3000` → use `??` (port could be 0) ### Design Principles - `src/services/user.ts` - 14 named exports → split into focused modules ### Summary | Category | Violations | Files | |----------------------|------------|-------| | General Patterns | X | N | | TypeScript/JS Idioms | Y | N | | Design Principles | Z | N | | **Total** | **X+Y+Z** | **N** | ``` ### Step 3: Fix Apply refactorings. For each fix: 1. Verify the change preserves existing behaviour 2. Keep changes minimal — only fix the identified issue 3. Do not introduce new abstractions unless clearly warranted
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.