chisle-review — Claude Code skill: code review
A Claude Code skill that spots over-engineering in a diff or file. It runs when asked to review for bloat or called with /chisle-review.
MIT ★ 1,250 updated 2026-11-14
npx skills add JayPokale/Chisle --skill chisle-review -a claude-codeWhat chisle-review does
The skill reviews a diff or file for code that can be removed or simplified. It flags one-off abstractions, custom versions of standard-library functions, unnecessary dependencies, and scaffolding with no current caller. It also catches verbose code that a platform feature, such as CSS or a database constraint, can replace.
Findings appear one per line, with a file path, line number, and a simpler alternative. There is no preamble or praise. The final line gives the finding count and an estimate of removable lines. It excludes trust-boundary validation, error handling that prevents data loss, security and accessibility code, and requirements explicitly set by the task.
What it helps with
- spot abstractions with only one implementation
- replace hand-built utilities with standard-library functions
- remove options that never vary
- trim code already handled by a platform feature
Example prompts for the agent
- Review this diff for bloat with chisle review.
- Check
src/cache.jsfor code that could be simplified. /chisle-review— find what can be removed from this file.
How to install chisle-review
1Skills CLI (Vercel)
npx skills add JayPokale/Chisle --skill chisle-review -a claude-code2Manually: put the files in place
~/.claude/skills/chisle-review/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/chisle-review/
1Skills CLI (Vercel)
npx skills add JayPokale/Chisle --skill chisle-review -a codex2Manually: put the files in place
.agents/skills/chisle-review/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add JayPokale/Chisle --skill chisle-review -a cursor2Manually: put the files in place
.cursor/skills/chisle-review/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install JayPokale/Chisle skills/chisle-review2Manually: put the files in place
.github/skills/chisle-review/SKILL.md1Skills CLI (Vercel)
npx skills add JayPokale/Chisle --skill chisle-review -a gemini-cli2Platform CLI
gemini skills install https://github.com/JayPokale/Chisle --path skills/chisle-reviewManually: put the files in place
.devin/skills/chisle-review/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add JayPokale/Chisle --skill chisle-review -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about chisle-review
How do I install chisle-review in Claude Code?
Run npx skills add JayPokale/Chisle --skill chisle-review -a claude-code. The skill file is installed at ~/.claude/skills/chisle-review/SKILL.md.
What does chisle-review do?
It checks diffs and files for overbuilt abstractions, hand-written replacements for standard functions, and verbose code. Findings are listed by line and followed by an estimate of removable lines.
What does chisle-review leave out of its findings?
It skips trust-boundary validation, error handling that prevents data loss, security and accessibility code, and anything explicitly required by the task.
Source text
SKILL.md · MIT
--- name: chisle-review description: > Review a diff or file through the Chisle lens: flag over-engineering, speculative abstractions, reinvented stdlib, and verbose code that a lazier approach would shrink. One finding per line, no praise. Use when the user says "chisle review", "review this for bloat", or invokes /chisle-review. --- # Chisle review Review the diff/file for **what could be deleted or simplified**, not for style nits. ## What to flag - Abstraction with one implementation (interface/factory/wrapper for a single case) - Reinvented stdlib (hand-rolled debounce, deep-clone, groupBy, date math) - New dependency for what a few lines or an installed dep already does - Config/option that never varies - Speculative "for later" scaffolding with no current caller - Verbose code where a native platform feature (CSS, DB constraint, `<input type>`) does it ## What NOT to flag - Input validation at trust boundaries - Error handling that prevents data loss - Security / accessibility code - Anything the task explicitly required ## Output format One finding per line. No preamble, no praise. ``` path:line: <what's over-built>. <the lazier replacement>. ``` Example: ``` cache.js:12: ApiCacheManager class for one call site. Replace with lru_cache / a Map. search.js:40: hand-rolled debounce util. setTimeout+clearTimeout inline is enough. ``` End with a one-line verdict: `N findings. Est. <X> lines removable.`
© JayPokale · MIT · JayPokale/Chisle