cleanup-codebase

Remove dead fields, redundant wrappers, and stale configurations from code.

5|2|Updated Nov 17, 2025

Search Tags:#codebase #cleanup #atomic-commit #local-change #dead-fields #redundant-wrappers

Ready to run

npx skills add https://github.com/OutlineDriven/odin-gemini-cli-extension --skill cleanup-codebase

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: cleanup-codebase
Source: https://github.com/OutlineDriven/odin-gemini-cli-extension/tree/main/skills/cleanup-codebase
Command: npx skills add https://github.com/OutlineDriven/odin-gemini-cli-extension --skill cleanup-codebase

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reduces concepts, duplication, and ceremony in internal code by removing dead fields, redundant wrappers, and speculative abstractions. It helps you stay close to nearby changes without polluting the public API.

Core Features & Use Cases

Identify dead fields, unused assignments, and wrappers that add no value.
Inline simple wrappers and delete the redundant abstractions to collapse local boundaries.
Ensure changes are atomic and localized to the nearby path, preserving behavior while simplifying the codebase.

Quick Start

Start by scanning the nearby code path you are editing and apply the cleanup rules to remove dead fields, wrappers, and stale config while preserving functionality.

Frequently Asked Questions about cleanup-codebase

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

FAQPage Schema

How do I remove dead code and redundant wrappers without breaking the public API?▼

Dead code cleanup targets internal modules by pruning dead fields and inlining redundant wrappers, ensuring changes are atomic and localized to preserve the public API behavior. It simplifies the codebase safely within scope.

What is the best way to clean up speculative abstractions in a local code path?▼

Cleaning up speculative abstractions involves identifying unused assignments and unnecessary indirection in the nearby path you are editing. It collapses local boundaries by deleting redundant wrappers while adhering to local boundary rules for safe cleanup.

Can I simplify internal code without changing external functionality?▼

Yes, you can simplify internal code by removing dead fields, stale configurations, and redundant wrappers. It applies atomic changes with localized impact to prune dead weight without altering the public API or changing behavior.

When should I prune dead fields and unnecessary indirection in my codebase?▼

You should prune dead fields and unnecessary indirection when editing an existing module to reduce concepts, duplication, and ceremony. It helps you stay close to nearby changes without polluting the public API.

Does codebase cleanup require atomic commits for safe localized changes?▼

Codebase cleanup enforces atomic changes and localized impact to ensure safe pruning of dead weight. It applies when editing an existing module, removing redundant abstractions while preserving functionality and adhering to local boundary rules.