dead-code

Identify and remove dead code, unused dependencies, and internal exports.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/arvindbattula/my-agent-config --skill dead-code-arvindbattula
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dead-code
Source: https://github.com/arvindbattula/my-agent-config/tree/main/skills/dead-code
Command: npx skills add https://github.com/arvindbattula/my-agent-config --skill dead-code-arvindbattula

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Clean codebases by identifying and removing dead code, unused dependencies, and internal exports, reducing maintenance burden and build times.

Core Features & Use Cases

  • Automated dead-code discovery across large codebases
  • Dependency hygiene: prune unused dependencies and devDependencies
  • Export cleanup to minimize public surface area and risk

Quick Start

Run npx knip to identify and remove unused files, dependencies, and exports from the project.

Frequently Asked Questions about dead-code

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

FAQPage Schema
How do I find and remove dead code in a large monorepo?

Unused npm dependencies and devDependencies are pruned through automated dependency hygiene. A guided knip workflow identifies unused packages and applies staged fixes to safely remove them from your project.

What is the best way to clean up unused internal exports in a codebase?

Dead code cleanup applies to monorepos and large codebases across development workflows. It enables scalable code cleanup and dependency hygiene without requiring specialized prerequisite environments.

How do I run knip to clean up unused files and exports?

Run npx knip to identify and remove unused files, dependencies, and exports from your project. This guided process provides configuration hints and validation checks for safe pruning.

What are the limitations of automated dead code removal?

Automated dead code removal requires careful validation to avoid breaking dynamic imports. The process mitigates this by using staged fixes and configuration hints to ensure safe pruning of internal exports.