Refactor
Claude Code skills for git workflows, GitHub automation, security audits, code refactoring, and project tooling
npx -y skills add tartinerlabs/skills --skill refactorAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 7 stars7 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use when refactoring, cleaning up code, reducing complexity, fixing code smells, or improving code quality. Audits code for dead code, nesting, and patterns.
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
1.5 KB, as published. Nobody here has run it
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:
- Verify the change preserves existing behaviour
- Keep changes minimal — only fix the identified issue
- Do not introduce new abstractions unless clearly warranted