Analyze code diffs and propose concrete deletions with rationale.
npx skills add https://github.com/rodacato/kwik-e-dev --skill simplify-rodacato
Please help me install this Agent Skill. Skill: simplify Source: https://github.com/rodacato/kwik-e-dev/tree/main/plugins/lifecycle/skills/simplify Command: npx skills add https://github.com/rodacato/kwik-e-dev --skill simplify-rodacato
Reviews changed code (or a diff) and removes what doesn't earn its keep — dead code, premature abstractions, unnecessary indirection, speculative flexibility, over-defensive guards. Produces concrete deletion suggestions with rationale. Use after writing a feature and before opening the PR. Use when a diff feels too large for what it accomplishes. Use when reviewing code that "works" but feels heavy. Use as a self-audit before declaring a task done.
Run the simplification workflow on your diff to surface dead code and unnecessary abstractions for deletion suggestions.
High-intent search queries and answers about installing and using this skill.
To remove dead code in a diff before a pull request, analyze the changed code to identify unnecessary indirection and speculative flexibility. This process maps the diff, applies a discretionary-change checklist, and surfaces concrete deletion suggestions with rationale.
Reducing code bloat in a feature diff involves auditing the changed code for premature abstractions and over-defensive guards. A formal simplification process identifies discretionary changes that inflate the surface area and proposes concrete deletions.
Diff analysis identifies premature abstractions by mapping the changed code and applying a checklist to evaluate speculative flexibility. It then documents proposed deletions with rationale to streamline the codebase and reduce risk before review.
Yes, you can use this simplification workflow to self-audit code across diverse codebases and teams. It is designed for pre-PR audits on feature diffs, providing deletion suggestions that work when a diff feels too heavy for what it accomplishes.
You should perform a pre-PR audit to trim unnecessary indirection after writing a feature and before declaring the task done. Use it when changed code works but feels heavy, or when a diff seems too large for its intended outcome.
jk278Analyze git repositories to summarize commit history and file changes.
BrunoAMSilvaReviews pull requests and architectural proposals for defects and risks.
diego-tobalinaRefactor code automatically with pattern matching and safety checks.
BamoseDetect dead code and unused exports in TypeScript projects with knip, depcheck, and ts-prune.
