Simplify
Lean code review — works only from git diff, no file reads, no subagents. Fixes reuse, quality, and efficiency issues directly inline.From its SKILL.md
npx -y skills add andriar/pokemon-buddy-claude --skill simplifyAssembled 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.
- 1 stars1 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.6 KB, as published. Nobody here has run it
Goal
Review and fix the changed code for quality, reuse, and efficiency. Operate entirely from the diff — do not read whole files or spawn agents.
Step 1 — Get the diff
Run:
git diff HEAD
If the diff is empty, check staged changes:
git diff --cached
Work only from this output. Do not read any source files beyond what the diff shows.
Step 2 — Review the diff inline
Scan the changed lines for these issues, in priority order:
Reuse
- New function that duplicates an existing one visible in the diff context
- Inline logic that a function already shown in the diff could handle
- Hardcoded constant that matches one already visible in the diff
Quality
f'...'string with no{...}interpolation — remove thefprefix- Comment that describes WHAT the code does (not WHY) — delete it
- Local constant defined inside a function that never changes — hoist to module level
- Stale data read from a snapshot that was taken before the relevant mutations
Efficiency
- Dict/object lookup inside a loop where the key never changes — move it outside
- Repeated computation of the same value within a tight loop
- Unnecessary intermediate variables used only once
Step 3 — Fix directly
Apply every fix you found by editing the file. Do not explain each fix — just make the change.
If a finding is a false positive, skip it silently.
Step 4 — Report
One-line summary per fix made. If nothing needed fixing, say "Code is clean."