anti-overengineering-review

Reviews codebases for over-engineering and reports deletable code, dependencies, and abstractions.

Updated Jul 11, 2026
One-click install
npx skills add https://github.com/azishio/coding-skills --skill anti-overengineering-review-azishio
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: anti-overengineering-review
Source: https://github.com/azishio/coding-skills/tree/main/skills/anti-overengineering-review
Command: npx skills add https://github.com/azishio/coding-skills --skill anti-overengineering-review-azishio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Codebases accumulate unnecessary complexity over time: hand-rolled reimplementations of standard library functions, duplicate dependencies, speculative abstractions with a single implementation, and dead configuration. This Skill performs a focused review that finds exactly what to delete and what replaces it, producing a one-line-per-finding report. ## Core Features & Use Cases - Complexity-Only Audit: Hunts reinvented stdlib functionality, unneeded dependencies, speculative abstractions, and dead flexibility while explicitly excluding correctness, security, and performance concerns. - Tagged Findings: Each finding is tagged (delete, stdlib, native, yagni, shrink, library, dup-dep, convention) with the location, what to cut, and the concrete replacement. - Scoped or Whole-Tree Review: Scans the entire codebase by default, or limits the review to a named scope such as a diff, staged changes, a PR, specific files, or a module. - Use Case: Before a release, ask for an over-engineering audit of your repository and receive a ranked list like Cargo.toml:L18: dup-dep: reqwest and ureq both present. Keep reqwest. ending with a net line and dependency reduction estimate. ## Quick Start Review this codebase for over-engineering and tell me what can be deleted or replaced with standard library or existing dependencies.

Frequently Asked Questions about anti-overengineering-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review a codebase for over-engineering?▼

Invoke the review on the whole tree by default, or name a scope such as a diff, staged changes, a PR, files, or a module. The output is one line per finding with the location, what to cut, and what replaces it, ranked biggest cut first.

What kinds of unnecessary code does an over-engineering review find?▼

It finds hand-rolled standard library functionality, dependencies duplicating platform features, single-implementation abstractions, dead flags and config, wrappers that only delegate, duplicate dependencies for one concern, and code bypassing framework conventions.

Does this review also catch bugs and security issues?▼

No. Correctness bugs, security holes, and performance problems are explicitly out of scope and should be routed to a normal review pass. This review only hunts complexity and unnecessary code.

Will the review apply the suggested deletions automatically?▼

No. It is a one-shot report that lists findings and applies nothing. Each finding names the replacement, such as a standard library function or a mature library, so you can decide what to change.

When should I not flag code as over-engineered?▼

Do not flag validation at trust boundaries, error handling that prevents data loss, security, or accessibility. A single smoke test or assert-based self-check is the minimum, not bloat, and is never flagged for deletion.