ponytail-review

To detect over-engineering bloat in a pull request code diff, scan the changes for hand-rolled standard library functions, unneeded dependencies, and speculative abstractions. This process targets complexity reduction by outputting structured findings with file locations and net line savings scores.

Speculative abstraction and dead flexibility in code review refer to unnecessary complexity like single-implementation interfaces or unused extensible code patterns. Detecting these bloat types helps eliminate maintenance burden by replacing them with direct, standard library functionality.

You get structured findings for simplifying code changes by scanning diffs for bloat patterns and outputting one-line results. Each finding includes the file location, bloat type tag, cut target, exact replacement, and a net line savings score to quantify the simplification impact.

This code review approach does not check for correctness and security bugs. It focuses exclusively on complexity reduction and over-engineering detection, ensuring you remove unneeded dependencies and reinvented standard library functions without overlapping with security auditing tasks.

You can use this to find unneeded dependencies in any software project. It applies to code review workflows for pull requests and code changes across all platforms, identifying heavy libraries imported for simple checks that standard native APIs can handle.

You should not use over-engineering detection when you need to validate functional correctness, fix security vulnerabilities, or enforce architectural patterns. This scanning mechanism is strictly limited to identifying bloat like hand-rolled utilities and speculative abstractions for simplification.