code-slimming

Audit codebases for dead code, redundant logic, and unnecessary wrappers.

2|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/iuliandita/skills --skill code-slimming
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-slimming
Source: https://github.com/iuliandita/skills/tree/main/skills/code-slimming
Command: npx skills add https://github.com/iuliandita/skills --skill code-slimming

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill identifies opportunities to reduce codebase bloat, maintenance burden, and technical debt by flagging dead code, redundant logic, and unnecessary wrappers without altering system behavior.

Core Features & Use Cases

  • Dead Code Detection: Identifies unused functions, variables, imports, and orphan files that can be safely removed.
  • Redundancy Audit: Flags duplicate code blocks and per-element function copies that can be collapsed into loops or lookup tables.
  • Wrapper & Comment Cleanup: Highlights inert try/catch blocks and noisy comment walls that add bytes without signal.

Quick Start

Use the code-slimming skill to audit the current repository for dead code and redundant logic.

Frequently Asked Questions about code-slimming

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

FAQPage Schema
How do I find and remove dead code in my repository?

You can find dead code by auditing your repository to identify unused functions, variables, imports, and orphan files. This process flags safe, behavior-preserving opportunities to reduce codebase size during refactoring.

What is the best way to audit a codebase for redundant logic and technical debt?

Auditing for redundant logic involves scanning for duplicate code blocks and per-element function copies. This flags opportunities to collapse redundant wrappers into loops or lookup tables, effectively reducing technical debt.

Does code refactoring for size reduction work across any programming language?

Yes, behavior-preserving size reduction applies across any programming language. The audit identifies unnecessary wrappers and inert try/catch blocks universally, ensuring safe repository cleanup regardless of your specific tech stack.

How do I clean up noisy comment walls and unnecessary wrappers without altering system behavior?

You can clean up unnecessary wrappers and noisy comment walls by auditing for inert try/catch blocks and comments that add bytes without signal. This structural analysis provides validation-backed refactor recommendations for safe removal.

When should I not use a structural analysis approach for repository cleanup?

Avoid structural analysis for repository cleanup when your goal involves altering system behavior rather than reducing size. This approach focuses strictly on behavior-preserving refactoring by removing dead code, redundant logic, and unnecessary wrappers.