reducing-entropy

To reduce codebase size, this Skill evaluates your code to identify and recommend deletion of unnecessary functions, features, and abstractions. It actively seeks removal opportunities, prioritizing a smaller final codebase over writing new code.

Codebase entropy reduction minimizes total code by focusing on deletion and simplification. It combats the natural tendency for codebases to grow unnecessarily, lowering maintenance overhead by removing rarely used features rather than writing new code to maintain them.

You should prioritize deleting features when code bloat has occurred or is a risk. If a feature is rarely used and requires significant new code to maintain, evaluating its complete removal reduces overall codebase size and minimizes future entropy.

The best way to measure success in simplification is by tracking the reduction in lines of code. This Skill applies a bias toward removal, measuring its effectiveness strictly by how much it shrinks the final codebase state through targeted deletions.

Yes, you can evaluate removing specific features like user_profile_v1. The Skill assesses whether individual features can be deleted entirely to reduce total code, actively recommending removal when the maintenance cost outweighs the feature's value.

Removing abstractions and unused code targets unnecessary features to minimize the final codebase state. While it prioritizes deletion over addition, it evaluates the impact of removing functionality to ensure only non-essential code is recommended for removal.