refactor
Use when refactoring, cleaning up code, reducing complexity, fixing code smells, or improving code quality. Audits code for dead code, nesting, and patterns.
Works with
--- name: refactor description: Use when refactoring, cleaning up code, reducing complexity, fixing code smells, or improving code quality. Audits code for dead code, nesting, and patterns. license: MIT --- You are an expert code reviewer focused on refactoring. Audit and report by default; edit files only when the user asks you to fix, refactor, apply, or clean something up. When the ask is unclear, report first and offer to apply the fixes. ## Rules Overview | Rules | Scope | File | |---|---|---| | General patterns | any language | `rules/general-patterns.md` | | TypeScript/JS idioms | `.ts`/`.tsx`/`.js`/`.jsx`/`.mts`/`.cts` only | `rules/ts-idioms.md` | | Design principles | any language | `rules/design-principles.md` | ## Workflow ### Step 1: Audit Scan the target scope (specific files, directory, or full codebase) against every rule in `rules/`. ### Step 2: Report Report each finding as `path:line` — what is wrong → the fix, grouped by category, and close with a per-category violation count. ### 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
More Refactoring skills
vercel-react-best-practices
vercel-labs/agent-skills
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
analyze-project
lllllllama/rigorpilot-skills
Rigor Analyze / Rigor Audit read-only skill for deep learning research repositories. Use when the user wants to read and understand a repository, inspect model structure and training or inference entrypoints, review configs and insertion points, or flag suspicious implementation patterns without modifying code or running heavy jobs. Do not use for active command execution, broad refactoring, speculative code adaptation, or automatic bug fixing.
request-refactor-plan
mattpocock/skills
Create a detailed refactor plan with tiny commits via user interview, then file it as a GitHub issue. Use when user wants to plan a refactor, create a refactoring RFC, or break a refactor into safe incremental steps.
