cruft-code-sweep

Audit codebases for dead code and deprecated patterns using Git history analysis.

1|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/kozyszoo/antigravity-handson --skill cruft-code-sweep-kozyszoo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cruft-code-sweep
Source: https://github.com/kozyszoo/antigravity-handson/tree/main/.claude/skills/cruft-code-sweep
Command: npx skills add https://github.com/kozyszoo/antigravity-handson --skill cruft-code-sweep-kozyszoo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automatically identifies and verifies unnecessary, outdated, or redundant code within a codebase, helping to reduce technical debt and improve maintainability.

Core Features & Use Cases

  • Automated Cruft Detection: Uses specialized agents to scan for dead code, deprecated patterns, and commented-out blocks.
  • Contextual Analysis: Leverages Git history to understand the age and rationale behind code segments.
  • Safety Verification: Ensures that identified cruft can be safely removed without introducing regressions.
  • Use Case: Before a major release, run this Skill to identify and remove any lingering TODO comments, unused functions, or old compatibility code that is no longer needed, ensuring a cleaner and more efficient codebase.

Quick Start

Run the cruft-code-sweep skill to audit the current project for dead code.

Frequently Asked Questions about cruft-code-sweep

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

FAQPage Schema
How do I find and remove dead code in my codebase before a release?

You can find and remove dead code by running an automated code audit that scans for unused functions, deprecated patterns, and commented-out blocks, then verifies each item can be safely deleted without causing regressions.

What is the best way to detect technical debt and cruft across multiple programming languages?

Detect technical debt and cruft across multiple languages by leveraging pattern matching and Git history analysis to identify outdated compatibility code, unused segments, and deprecated structures for safe code cleanup.

How does historical Git analysis help with safe code cleanup?

Historical Git analysis helps with safe code cleanup by determining the age and original rationale behind specific code segments, providing context to ensure cruft removal does not introduce regressions.

Can I use automated cruft detection for deprecated patterns and compatibility code?

Yes, automated cruft detection scans codebases specifically for deprecated patterns and lingering compatibility code, using specialized agents to verify identified segments are no longer needed before removal.

What are the limitations of using automated refactoring for technical debt reduction?

Automated refactoring for technical debt reduction relies on pattern matching and historical analysis, meaning complex or deeply intertwined logic might require manual review to guarantee safe removal without regressions.