clean-helper

Identify and remove dead code and deprecated branches via static analysis.

Updated May 15, 2026
One-click install
npx skills add https://github.com/j-show/ai-everything --skill clean-helper
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clean-helper
Source: https://github.com/j-show/ai-everything/tree/main/skills/clean-helper
Command: npx skills add https://github.com/j-show/ai-everything --skill clean-helper

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill solves the risk of breaking production code during cleanup by providing a structured, evidence-first workflow for identifying and removing dead code, deprecated branches, and redundant logic.

Core Features & Use Cases

  • Evidence-Based Cleanup: Requires proof of unreachability (call graphs, reference checks) before any deletion occurs.
  • Safety Guardrails: Implements a mandatory confirmation step and verification phase to ensure behavior-preserving changes.
  • Use Case: Use this when you need to prune a large legacy codebase, remove deprecated feature flags, or delete unused exports without accidentally breaking runtime dependencies or public APIs.

Quick Start

Invoke the clean-helper skill to identify and remove unused functions and redundant logic within the current directory.

Frequently Asked Questions about clean-helper

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

FAQPage Schema
How do I safely remove dead code from a legacy codebase without breaking production?

Dead code removal requires an evidence-first workflow that gathers proof of unreachability through static analysis and call-graph verification before applying any destructive changes. A mandatory confirmation step ensures behavior-preserving modifications during refactoring.

What is the best way to prune deprecated feature flags and redundant logic?

Pruning deprecated feature flags involves rigorous evidence gathering through call-graph verification and reference checks to confirm unreachability. This structured cleanup process implements safety guardrails and a verification phase to prevent accidental runtime breakage.

Can I use static analysis to identify unused exports before deleting them?

Static analysis identifies unused exports by verifying call graphs and checking references within a scoped codebase. This evidence-based cleanup approach requires proof of unreachability before any deletion occurs, protecting public APIs and runtime dependencies.

Does this cleanup workflow require a confirmation step before modifying code?

The cleanup workflow implements a mandatory confirmation step and verification phase to ensure behavior-preserving changes. Safety guardrails require rigorous evidence gathering through static analysis before applying any destructive modifications like dead code removal.

When do I need call-graph verification for refactoring legacy code?

Call-graph verification is needed when removing dead code, deprecated branches, or redundant logic from a legacy codebase. It provides the rigorous evidence required to prove unreachability before executing destructive changes during maintenance and dependency cleanup tasks.