code-pruning

Detect and remove dead code, unused dependencies, and codebase bloat.

Updated Feb 17, 2026
One-click install
npx skills add https://github.com/smileynet/code-spice --skill code-pruning
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-pruning
Source: https://github.com/smileynet/code-spice/tree/main/skills/code-pruning
Command: npx skills add https://github.com/smileynet/code-spice --skill code-pruning

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill addresses the accumulation of unused code, dependencies, and bloat within a codebase, which can lead to increased maintenance overhead, slower build times, and a larger attack surface.

Core Features & Use Cases

  • Dead Code Detection: Identifies and helps remove code that is never executed.
  • Dependency Pruning: Finds and assists in removing unused libraries and packages.
  • Bloat Metrics: Provides insights into codebase size and complexity trends.
  • Use Case: During a regular code review or before a major refactor, use this Skill to scan the project for any functions, classes, or dependencies that are no longer in use, ensuring a leaner and more maintainable codebase.

Quick Start

Run a dead code scan on the current project to identify unused code.

Frequently Asked Questions about code-pruning

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

FAQPage Schema
How do I detect and remove dead code from my codebase?

Dead code detection scans your project to identify functions and classes that are never executed. This Skill uses static and dynamic analysis to find unused code blocks, helping you eliminate technical debt and reduce maintenance overhead safely.

What is the best way to find and prune unused dependencies?

Dependency pruning finds and assists in removing unused libraries and packages through systematic dependency audits. This Skill identifies unused dependencies that increase build times and expand your attack surface, ensuring a leaner and more maintainable codebase.

How do I track codebase bloat and complexity trends?

Tracking codebase bloat requires monitoring size and complexity metrics over time. This Skill provides bloat metrics insights, enabling you to measure codebase health and identify accumulation of unused code and dependencies before they cause significant maintenance issues.

When should I scan my project for technical debt and unused code?

Scanning for technical debt is recommended during regular code reviews or before a major refactor. This Skill helps identify unused functions, classes, and dependencies to prevent antipatterns like Lava Flow and ensure systematic code reduction.

Can I use static and dynamic analysis together for code pruning?

Static and dynamic analysis are both supported for detecting dead code and unused dependencies. This Skill combines dependency audits and bloat metric tracking to address challenges in identifying and eliminating technical debt through a systematic code reduction process.