tartinerlabs/skills

refactor

Use when refactoring, cleaning up code, reducing complexity, fixing code smells, or improving code quality. Audits code for dead code, nesting, and patterns.

First seen Feb 15, 2026

Installation

$ npx skills add tartinerlabs/skills --skill refactor

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from tartinerlabs/skills · top by installs.

npx skills add tartinerlabs/skills

Browse all from tartinerlabs/skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 8
License LICENSE
Default branch main
Open issues 5
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

LicenseMIT
CompatibilityAny language; general + design rules always apply, the TS/JS idiom rules apply only to TS/JS files
Allowed toolsRead Glob Grep Edit
More metadata
short-description
Refactor and reduce code complexity.

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,528 B
  • docs SUMMARY.md 170 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 310 installs

SKILL.md

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