Reviews code and docs for 11 categories of unnecessary complexity.
npx skills add https://github.com/vatsal2210/claude-skills --skill simplify-vatsal2210
Please help me install this Agent Skill. Skill: simplify Source: https://github.com/vatsal2210/claude-skills/tree/main/simplify Command: npx skills add https://github.com/vatsal2210/claude-skills --skill simplify-vatsal2210
Simplify reduces unnecessary complexity in post-implementation code, docs, and scripts by identifying duplication, dead abstractions, over-engineering, clever/opaque constructs, state sprawl, import bloat, test cruft, config duplication, and prose drift across files. It helps teams avoid long-term maintenance tax by finding easy wins (inline a one-off helper, remove a needless retry loop) and by surfacing judgment calls that require human approval.
Ask simplify to review the changed files in this session and produce a Phase 2 findings report listing categorized simplification suggestions.
High-intent search queries and answers about installing and using this skill.
You can identify over-engineering and dead abstractions by running a post-implementation code review that classifies complexity into eleven predefined categories. The review generates a report with file:line ranges, proposed replacements, and risk ratings to help you prune unnecessary abstractions without modifying code directly.
The best way to review changed files for code duplication and test cruft is to apply a session-scoped review that targets only recently modified files. This approach categorizes findings into specific areas like test cruft and config duplication, outputting a report with estimated savings and risk levels to guide precise refactoring.
To reduce state sprawl and import surface issues after a feature lands, perform a targeted post-implementation review. This process scans your changed code to surface findings across eleven complexity categories, providing concise now versus proposed comparisons and risk ratings for safe refactoring.
Yes, you can refactor a pasted code snippet for readability without scanning the whole project. The review process accepts a pasted snippet as its scope, analyzing it for unclear clever code and over-engineering to produce a focused findings report with proposed replacements and savings estimates.
No, this code review approach does not automatically fix premature error handling and comment rot. It operates in a read-only Phase 2 report mode, identifying these issues alongside cross-file divergence and providing proposed replacements and risk ratings for human approval before any edits are made.
jeremy-newhouseValidate code changes with severity-filtered findings across selected rigor modes.
DevelopersGlobalRefactor legacy code with behavior-preserving micro-steps and test adherence.
paimlAnalyze code quality and technical debt with PMAT metrics.
nikhillinitDetect and prioritize technical debt with configurable thresholds and SQALE metrics.
