absolute-prune

Remove dead code and unused dependencies with tool evidence and tests.

207|31|Updated Mar 14, 2026
One-click install
npx skills add https://github.com/maddhruv/absolute --skill absolute-prune
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: absolute-prune
Source: https://github.com/maddhruv/absolute/tree/main/skills/absolute-prune
Command: npx skills add https://github.com/maddhruv/absolute --skill absolute-prune

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill addresses the issue of dead code and unused dependencies in a codebase, ensuring that the codebase remains clean and efficient.

Core Features & Use Cases

  • Dead Code and Dependency Cleanup: Removes unused dependencies, unreferenced exports, unreachable code, and orphaned files.
  • Tool Evidence: Ensures that every removal is backed by tool evidence, applied in reversible waves.
  • Safety and Verification: Runs on green main and verifies changes through tests after each wave.
  • Use Case: After a refactor, use this Skill to remove dead code and unused dependencies, ensuring that the codebase is clean and maintainable.

Quick Start

Run the absolute-prune skill to remove dead code and unused dependencies from your codebase.

Frequently Asked Questions about absolute-prune

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

FAQPage Schema
How do I safely remove dead code and unused dependencies after a refactor?

To safely remove dead code after a refactor, use a tool that operates on a green main branch and verifies changes through tests after each removal wave. This approach ensures your codebase remains stable while cleaning unreferenced exports and unused dependencies.

What is the best way to clean up orphaned files and unreachable code in a repository?

The best way to clean up orphaned files and unreachable code is to apply tool-evidence-based removals in reversible waves. This method verifies each change through tests, ensuring that only genuinely dead code is removed without breaking existing functionality.

Does dead code removal require a specific repository state before starting?

Dead code removal requires a green main branch before starting. The process verifies changes through tests after each removal wave, ensuring that your codebase maintains a clean, passing state throughout the cleanup operation.

Can I automate unused dependency cleanup without breaking my codebase?

Yes, you can automate unused dependency cleanup without breaking your codebase by using tool evidence for every removal. By applying changes in reversible waves and running tests after each step, the process maintains codebase health and efficiency safely.

What types of dead code can be removed during a codebase cleanup?

During a codebase cleanup, you can remove unused dependencies, unreferenced exports, unreachable code, and orphaned files. This comprehensive removal ensures your codebase remains clean and efficient after major refactoring work.

When should I use an automated repo cleanup tool for dead code removal?

You should use an automated repo cleanup tool for dead code removal during post-refactor maintenance. It addresses the accumulation of unused dependencies and dead code, ensuring your codebase remains clean, efficient, and maintainable over time.