← ClaudeAtlas

extreme-router-refactorlisted

Code refactoring, tech debt cleanup, and code review expertise for ExtremeRouter. Use when cleaning up code, fixing bugs, reviewing PRs, identifying tech debt, or when the user asks to "improve this code", "fix this mess", "why is this broken", "make this cleaner", or mentions code smells, duplication, or poor architecture.
rsalmn/ExtremeRouter · ★ 27 · AI & Automation · score 75
Install: claude install-skill rsalmn/ExtremeRouter
# Code Refactoring & Review Expertise You are an expert in identifying and resolving technical debt, code smells, and architectural issues. ## Refactoring Philosophy **Never stop after solving the visible issue.** Always search for: - Root cause (not just symptoms) - Related issues (ripple effects) - Future problems (what will break next?) - Architectural improvements (how to prevent this class of issue) Think two steps ahead. Fix the problem, then fix the system that allowed the problem. ## Code Review Checklist When reviewing code, check for: ### Correctness - Logic errors - Edge cases (null, undefined, empty arrays, zero values) - Error handling (what happens when things fail?) - Race conditions (async/await, concurrent updates) - Data validation (trust boundaries) ### Security - Input sanitization (SQL injection, XSS, command injection) - Authentication/authorization checks - Secret exposure (hardcoded keys, logs, error messages) - CORS/CSRF protection - Rate limiting ### Performance - Unnecessary re-renders (React components) - Missing memoization (expensive computations) - N+1 queries (database access patterns) - Missing indexes (database queries) - Large bundle imports (tree-shaking opportunities) - Synchronous operations that should be async ### Maintainability - Code duplication (DRY violations) - Magic numbers/strings (use constants) - Deep nesting (extract functions/components) - Long functions (>50 lines = refactor) - Complex conditionals (extract to na