refactor-project
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".
What this skill does
# Refactor Project Command Execute automated project-wide refactoring using `refactor:code-simplifier` agent with cross-file optimization focus. ## Pre-operation Checks **Goal**: Ensure project-wide execution is explicit and reproducible. **Actions**: 1. Run `git rev-parse --is-inside-work-tree`; if false, inform user that project-wide mode requires a git workspace 2. Record current revision with `git rev-parse --short HEAD` and include it in final summary for rollback context 3. Ignore command arguments and proceed with full-project discovery ## Phase 1: Analyze Project Scope **Goal**: Discover all code files and display scope summary. **Actions**: 1. Find all code files using Glob patterns for common extensions 2. Filter out `node_modules/`, `.git/`, `dist/`, `build/`, `vendor/`, `.venv/` 3. Group files by language/extension and identify primary source directories 4. Display scope summary (file count, languages, directories) then proceed automatically See `references/scope-analysis.md` for exclusion patterns and edge cases. ## Phase 2: Launch Refactoring Agent **Goal**: Execute `refactor:code-simplifier` agent with project-wide scope and cross-file focus. **Actions**: 1. Launch `refactor:code-simplifier` agent with all discovered code files 2. Pass cross-file optimization emphasis: duplication reduction, consistent patterns 3. Pass aggressive mode flag for legacy code removal 4. Agent auto-loads `refactor:best-practices` skill and applies language-specific patterns See `references/agent-configuration.md` for detailed Task parameters. ## Phase 3: Summary **Goal**: Report comprehensive summary of project-wide changes. **Actions**: 1. Report total files refactored (count and percentage of project) 2. List changes categorized by improvement type and cross-file improvements made 3. List best practices applied and legacy code removed 4. Suggest test suite to run and recommend reviewing changes in logical groups 5. Provide safer rollback command tied to recorded baseline (for example: `git restore --worktree --staged .`) See `references/output-requirements.md` for detailed summary format. ## Requirements - Execute immediately after displaying scope (no confirmation needed) - Refactor entire project across all discovered code files - Prioritize cross-file duplication reduction and consistent patterns - Preserve behavior and public interfaces unless user explicitly requests a behavior change
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.