deadcode

Detect and remove dead code across JavaScript, Python, Go, and Rust projects.

Updated Feb 17, 2026
One-click install
npx skills add https://github.com/Objective-Arts/lens-dist --skill deadcode-objective-arts
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deadcode
Source: https://github.com/Objective-Arts/lens-dist/tree/main/canon/deadcode
Command: npx skills add https://github.com/Objective-Arts/lens-dist --skill deadcode-objective-arts

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps developers identify and remove unused code, dependencies, and files from their projects, leading to cleaner, more maintainable, and efficient codebases.

Core Features & Use Cases

  • Detects dead code: Finds unused exports, unreachable code, and orphaned files.
  • Manages dependencies: Identifies and helps remove unused package dependencies.
  • Polyglot support: Works across JavaScript/TypeScript, Python, Go, and Rust.
  • Use Case: Before a major release, use this Skill to clean up any code that is no longer called or dependencies that are no longer imported, reducing project bloat.

Quick Start

Use the deadcode skill to find all unused code in the current project.

Frequently Asked Questions about deadcode

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

FAQPage Schema
How do I find and remove unused code and dependencies across multiple programming languages?

Static analysis identifies dead code across JavaScript, TypeScript, Python, Go, and Rust by detecting unused exports, unreachable code, and orphaned files while respecting @keep markers and filtering test files.

What is the best way to clean up dead code before a major software release?

Running static analysis to detect unused exports, orphaned files, and unused dependencies reduces project bloat and improves maintainability before a major release.

How do I detect unused exports and unreachable code in a polyglot project?

Language-specific static analyzers like knip for JavaScript, vulture for Python, deadcode for Go, and cargo-udeps for Rust detect unused exports and unreachable code across polyglot projects.

Can I use static analysis to find unused dependencies in Python and Go projects?

Static analysis identifies unused dependencies in Python and Go projects using vulture and the deadcode analyzer, respectively, alongside support for JavaScript and Rust.

How do I prevent static analysis from flagging necessary code and test files as dead code?

Static analysis prevents false positives by respecting @keep markers to preserve necessary code and filtering out test files alongside node_modules and vendor directories.