Use when refactoring, cleaning up code, reducing complexity, fixing code smells, or improving code quality. Audits code for dead code, nesting, and patterns.
Installs into .claude/skills of the current project.
Are you the author of Refactor?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/tartinerlabs-refactor)
---
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
allowed-tools: Read Glob Grep Edit
model: sonnet
effort: high
context: fork
agent: general-purpose
compatibility: Any language; general + design rules always apply, the TS/JS idiom rules apply only to TS/JS files
metadata:
short-description: Refactor and reduce code complexity.
---
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
