dead-code

Detect unused exports, imports, variables, and unreachable branches in TypeScript, Python, and Go projects.

Updated Apr 17, 2026
One-click install
npx skills add https://github.com/smallorbit/smallorbit-plugins --skill dead-code-smallorbit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dead-code
Source: https://github.com/smallorbit/smallorbit-plugins/tree/main/plugins/polishkit/skills/dead-code
Command: npx skills add https://github.com/smallorbit/smallorbit-plugins --skill dead-code-smallorbit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams identify and remove dead or unreachable code, reducing maintenance burden and improving readability and performance.

Core Features & Use Cases

  • Detects unused exports and imports across TypeScript, Python, and Go projects.
  • Flags dead variables, unreachable branches, and obsolete code blocks for review.
  • Use Case: When a feature is deprecated or refactored, run this Skill to clean up stale code paths and exports.

Quick Start

Run the dead-code eliminator against your repository to identify dead code and begin a review before deletions.

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 unused exports and dead code in a TypeScript project?

To find dead code in TypeScript, this Skill scans for unused exports, imports, and dead variables using language-aware tooling like ts-prune, proposing safe removals after validation.

What is the safest way to clean up unreachable branches and obsolete code blocks?

The safest way to clean up unreachable branches is a confirmation-based workflow that validates findings from static analysis tools before applying any code deletions to your repository.

Can I detect dead variables and unused imports across both Python and Go projects?

Yes, you can detect dead variables and unused imports across Python and Go projects by running this Skill, which leverages language-aware static analysis tools like pyflakes, ruff, and staticcheck.

Do I need to install static analysis tools like ruff or staticcheck before scanning?

Yes, you need language-aware tooling installed, as this Skill relies on tools like ts-prune, pyflakes, ruff, and staticcheck to accurately identify unused code and unreachable branches for review.

What are the limitations of using static analysis to prune dead code?

Static analysis limitations include potential false positives for dynamic code usage, requiring a confirmation-based workflow to manually validate flagged dead variables and obsolete blocks before deletion.