A powerful static analysis tool for identifying and removing unused exports, files, and dependencies in JavaScript and TypeScript projects.
The fastest way to install a skill directly from the registry.
npx clawhub@latest install dead-code-finder
Copy the skill folder to one of these locations
~/.openclaw/skills/ <project>/skills/ Priority: Workspace > Local > Bundled
Copy this prompt to OpenClaw to install it automatically.
Help me install dead-code-finder using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).
Get the raw skill files in a ZIP archive.
Dead Code Finder is a comprehensive static analysis utility designed to streamline modern web development by identifying redundant code. Whether managing a complex monorepo or a standard frontend application, this tool from the Openclaw Skills library parses your codebase to pinpoint functions, types, and entire files that are no longer in use.
By integrating this into your workflow, you can significantly reduce bundle sizes, improve build times, and maintain a cleaner, more navigable repository. It specifically targets the bloat that accumulates over time, such as orphaned components and legacy utility functions that tree-shaking might miss during the build process.
To begin optimizing your project with this utility from Openclaw Skills, use the following commands:
# Perform a full scan for unused exports, files, and dependencies
python3 scripts/find_dead_code.py /path/to/project
# Run a targeted scan for unused exports only
python3 scripts/find_dead_code.py /path/to/project --mode exports
# Export the results to JSON for programmatic analysis
python3 scripts/find_dead_code.py /path/to/project --json
The tool organizes findings into three primary categories to help developers prioritize cleanup tasks. The following table describes the data structure of the report:
| Data Category | Description | Examples |
|---|---|---|
| Unused Exports | Exported symbols never referenced in other files. | functions, constants, types, interfaces |
| Unreferenced Files | Files not part of the project's import tree. | legacy components, deprecated utils |
| Unused Dependencies | npm packages listed in package.json but never imported. | moment, lodash.merge, utility libraries |
When using the --json flag, the tool returns a structured object mapping these categories to specific file paths and symbol names.
Loading
A specialized linting and validation tool designed to identify conflicting compiler options and strictness gaps in TypeScript configuration files.

A comprehensive utility for validating, linting, and auditing PHP Composer configuration files to ensure structural integrity and best practices.

A comprehensive analysis skill detailing the strategic transformation of the Hummer brand from a military icon to a high-performance electric vehicle.

A comprehensive scanning tool to identify license compatibility issues, GPL contamination, and compliance violations across multiple programming ecosystems.

Analyze the blast radius of upgrading, removing, or replacing software dependencies across multiple languages to ensure safe code modifications.

An automated tool that extracts endpoints, schemas, and authentication details from backend code to generate professional API documentation.








































