Skip to content

a5c-ai/babysitter / library/specializations/code-migration-modernization/skills/dead-code-eliminator

dead-code-eliminator

Unverified

Identify and safely remove dead, unused, and unreachable code from codebases

Dead Code Eliminator Skill

Identifies and safely removes dead code, unused functions, unreachable code paths, and orphaned files from codebases to reduce complexity and maintenance burden.

Purpose

Enable safe dead code removal for:

  • Codebase simplification
  • Migration preparation
  • Technical debt reduction
  • Build size optimization
  • Maintenance cost reduction

Capabilities

1. Unused Function Detection

  • Find uncalled functions
  • Identify unused exports
  • Detect unreferenced methods
  • Map call graphs

2. Unreachable Code Identification

  • Analyze control flow
  • Find code after returns
  • Detect impossible conditions
  • Identify dead branches

3. Unused Variable Detection

  • Find unread variables
  • Identify write-only variables
  • Detect unused parameters
  • Flag shadowed variables

4. Orphan File Detection

  • Find unimported modules
  • Identify orphaned assets
  • Detect unused configuration
  • Map file dependencies

5. Safe Removal Verification

  • Verify no runtime references
  • Check dynamic imports
  • Validate reflection usage
  • Test after removal

6. Impact Analysis

  • Estimate removal scope
  • Calculate size reduction
  • Assess risk level
  • Document dependencies

Tool Integrations

ToolLanguageIntegration Method
ts-pruneTypeScriptCLI
unimportedJavaScriptCLI
deadcodePythonCLI
UCDetectorJavaEclipse Plugin
unusedRustCLI
deadcodeGoCLI
webpack-bundle-analyzerJavaScriptCLI

Output Schema

{
  "analysisId": "string",
  "timestamp": "ISO8601",
  "deadCode": {
    "functions": [
      {
        "file": "string",
        "name": "string",
        "line": "number",
        "confidence": "high|medium|low",
        "reason": "string"
      }
    ],
    "variables": [],
    "files": [],
    "unreachable": []
  },
  "impact": {
    "filesAffected": "number",
    "linesRemovable": "number",
    "estimatedSizeReduction": "string"
  },
  "risks": [],
  "recommendations": []
}

Integration with Migration Processes

  • code-refactoring: Pre-refactoring cleanup
  • legacy-decommissioning: Feature removal
  • monolith-to-microservices: Service extraction prep

Related Skills

  • static-code-analyzer: Combined analysis
  • code-smell-detector: Related smell detection

Related Agents

  • legacy-decommissioning-specialist: Uses for cleanup
  • code-transformation-executor: Executes removal
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 318kUpdated Claude CodeCodexUnverifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 318kUpdated Claude CodeCodexUnverifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 318kUpdated Claude CodeCodexUnverifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 318kUpdated Claude CodeCodexUnverifiedInstall