dead-code-check

Detects unused code, imports, functions, and variables across five languages.

53|1|Updated Dec 18, 2025
One-click install
npx skills add https://github.com/cosmix/loom --skill dead-code-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dead-code-check
Source: https://github.com/cosmix/loom/tree/main/skills/dead-code-check
Command: npx skills add https://github.com/cosmix/loom --skill dead-code-check

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill identifies and helps you remove dead code, ensuring that all implemented features are actually wired into your application and reducing maintenance overhead.

Core Features & Use Cases

  • Wiring Verification: Catches features that were implemented but never integrated into the codebase.
  • Code Quality Improvement: Identifies cleanup opportunities and reduces technical debt.
  • Use Case: After implementing a new API endpoint, use this Skill in your integration-verify stage to ensure the route is correctly registered and the handler function is called.

Quick Start

Run the dead-code-check skill to verify Rust code quality using clippy.

Frequently Asked Questions about dead-code-check

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

FAQPage Schema
How do I find unused functions and imports in my TypeScript project?

Dead code detection identifies unused functions and imports in TypeScript by providing language-specific commands and ignore patterns to verify code integration and reduce maintenance overhead.

What is the best way to verify Rust code quality and catch dead code?

Rust code quality verification catches dead code using clippy commands to identify unused variables and functions, ensuring implemented features are properly wired into the application.

Does dead code detection work with Python and Go codebases?

Dead code detection works with Python, Go, JavaScript, Rust, and TypeScript by providing language-specific fail patterns and commands to identify unused code across different codebases.

How can I automate code cleanup and remove unused variables during integration?

Automated code cleanup removes unused variables by running dead code checks in your integration-verify stage to ensure route handlers are registered and functions are called.

Why does my implemented API endpoint show up as dead code?

Implemented API endpoints show up as dead code when the route is not correctly registered or the handler function is never called, indicating incomplete wiring within the application.