skills.rest
ceshez
ceshezCOMMUNITY
Explore all skills by this author →
GitHub

reducing-entropy

Evaluate code changes by comparing final code volume before and after.

Updated Aug 23, 2026
Search Tags:#refactoring#technical debt#simplicity#code reduction#deletion bias#end-state metrics
One-click install
npx skills add https://github.com/ceshez/VELAR --skill reducing-entropy-ceshez
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reducing-entropy
Source: https://github.com/ceshez/VELAR/tree/main/.agents/skills/reducing-entropy
Command: npx skills add https://github.com/ceshez/VELAR --skill reducing-entropy-ceshez

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps you prevent a codebase from silently growing in size by making success depend on the final amount of code, not on the effort you put in or how “clean” the change feels.

Core Features & Use Cases

  • End-state code metric: Evaluates proposals by comparing total code (lines/functions/classes) before vs. after, rejecting changes that increase it.
  • Deletion-first decision framework: Forces answers to what you can remove and what becomes obsolete after the change.
  • Mindset loading gate: Requires you to load at least one philosophical mindset from the references directory before proceeding.
  • Manual-only control: Intended for explicit user requests to “reduce entropy” or “minimize code,” avoiding unintended aggressive simplification.

Quick Start

Ask the assistant to reduce entropy for your proposed change, and require it to first load a mindset from references/ before recommending deletions.

Frequently Asked Questions about reducing-entropy

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

FAQPage Schema
How do I evaluate refactoring proposals by final codebase size?▼

Evaluate refactoring by measuring total code volume, such as lines or functions, before versus after the change. Reject proposals that increase the overall codebase size, judging success by the resulting end state rather than perceived effort or cleanliness.

What is deletion bias in technical debt cleanup?▼

Deletion bias in technical debt cleanup forces you to identify what code can be removed and what becomes obsolete after a change. It prioritizes reducing total codebase size to lower bug risk and maintenance burden.

How do I decide what code to delete when minimizing technical debt?▼

Answer three core questions about the smallest solvable result and deletable portions. Load a philosophical mindset reference before proceeding to ensure aggressive simplification targets unnecessary code growth safely.

Can I automate code reduction for routine feature evaluation?▼

Code reduction using this method is manual-only and intended for explicit requests to minimize code. It avoids unintended aggressive simplification by requiring a user-initiated prompt to load a mindset reference before recommending deletions.

When should I avoid biasing toward deletion during refactoring?▼

Avoid deletion bias when a proposed change genuinely requires new code to deliver functionality. The framework rejects changes that increase total code volume, so it suits technical-debt cleanup and feature evaluation where reducing the end-state metric is the primary goal.

Related Skills

Explore More Software Engineering Skills→
RamonsDkaRamonsDka
1

reducing-entropy

Minimize codebase size by biasing toward deletion and simplification.

Community
Intermediate
imMamdouhaboammarimMamdouhaboammar

reducing-entropy

Evaluate refactoring changes for net decreases in code volume.

Community
Intermediate
dorriodorrio

ln-626-dead-code-auditor

Audit codebases for unreachable code, unused imports, variables, functions, and deprecated patterns.

Community
Intermediate
belokonmbelokonm
8

refactoring-specialist

Apply test-driven refactoring strategies to improve code readability and maintainability.

Community
Advanced