Simplify

Read source code and find opportunities to simplify, deduplicate, and consolidate. Apply changes after user approval.From its SKILL.md

Install

npx -y skills add kt3k/skills --skill simplify

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
3 stars3 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.

SKILL.md

1.3 KB, 285 tokens by cl100k_base, as published. Nobody here has run it

Arguments (optional)

<scope>: A file path, directory, or free-form description of the range to review (e.g. src/foo.ts, the auth module, lines 100-200 of bar.py).

Steps

Resolve the scope:
- If an argument is provided, use it as the review scope.
- If no argument is provided:
  - Check the current git branch (git rev-parse --abbrev-ref HEAD).
  - If the current branch is not main (e.g. main, master), use Current branch diff as the review scope.
  - Otherwise, ask the user explicitly which scope to use, using AskUserQuestion with these options:
    - Whole codebase — review all source code in the repository
    - Current branch diff — review changes in the current branch vs the main branch
    - Last commit — review changes in the most recent commit (git show HEAD)
    - Other — let the user specify a custom scope (free-form input)
- Do NOT proceed until the scope is determined.
Review: Read the source code in the resolved scope and identify areas that can be simplified, duplicated parts, and opportunities for refactoring or abstraction.
Apply changes after user approval.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most refactoring skills give in 285 tokens

Counted across 545 of the 587 authors here whose files we hold, read 2026-09-06

Run tests after each changein 61 of 545, across 59 files
Run tests before refactoringin 42 of 545
Revert immediately if tests failin 31 of 545, across 28 files
Perform refactoring in small stepsin 30 of 545, across 29 files
Write characterization tests for untested codein 21 of 545, across 19 files
Remove dead code and unused importsin 20 of 545
Identify code smellsin 20 of 545
Perform one refactoring at a timein 19 of 545
Commit after each successful refactoringin 17 of 545, across 15 files
Verify all tests pass after refactoringin 17 of 545
Keep refactoring separate from behavior changesin 16 of 545, across 14 files
Run the full test suitein 16 of 545

Said here and by no other author read

Resolve the review scope before proceeding
Identify areas for simplification and deduplication
Identify opportunities for refactoring or abstraction

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.